[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] r9966 - libmicrohttpd-docs/WWW
|
From: |
gnunet |
|
Subject: |
[GNUnet-SVN] r9966 - libmicrohttpd-docs/WWW |
|
Date: |
Fri, 8 Jan 2010 10:49:11 +0100 |
Author: grothoff
Date: 2010-01-08 10:49:11 +0100 (Fri, 08 Jan 2010)
New Revision: 9966
Modified:
libmicrohttpd-docs/WWW/microhttpd.html
Log:
fix
Modified: libmicrohttpd-docs/WWW/microhttpd.html
===================================================================
--- libmicrohttpd-docs/WWW/microhttpd.html 2010-01-06 19:33:50 UTC (rev
9965)
+++ libmicrohttpd-docs/WWW/microhttpd.html 2010-01-08 09:49:11 UTC (rev
9966)
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html401/loose.dtd";>
<html>
-<!-- This manual documents GNU libmicrohttpd version 0.4.2, last
-updated 11 October 2009. It is built upon the documentation in the
+<!-- This manual documents GNU libmicrohttpd version 0.4.4, last
+updated 4 December 2009. It is built upon the documentation in the
header file microhttpd.h.
@@ -15,28 +15,28 @@
Free Documentation License".
-->
-<!-- Created on October, 11 2009 by texi2html 1.78 -->
-<!--
-Written by: Lionel Cons <address@hidden> (original author)
+<!-- Created on January 8, 2010 by texi2html 1.82
+texi2html was written by:
+ Lionel Cons <address@hidden> (original author)
Karl Berry <address@hidden>
Olaf Bachmann <address@hidden>
and many others.
Maintained by: Many creative people.
Send bugs and suggestions to <address@hidden>
-
-->
<head>
-<title>The GNU libmicrohttpd Reference Manual: The GNU libmicrohttpd
Library</title>
+<title>The GNU libmicrohttpd Reference Manual</title>
-<meta name="description" content="The GNU libmicrohttpd Reference Manual: The
GNU libmicrohttpd Library">
-<meta name="keywords" content="The GNU libmicrohttpd Reference Manual: The GNU
libmicrohttpd Library">
+<meta name="description" content="The GNU libmicrohttpd Reference Manual">
+<meta name="keywords" content="The GNU libmicrohttpd Reference Manual">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
-<meta name="Generator" content="texi2html 1.78">
+<meta name="Generator" content="texi2html 1.82">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
pre.display {font-family: serif}
pre.format {font-family: serif}
pre.menu-comment {font-family: serif}
@@ -57,17 +57,16 @@
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
<a name="Top"></a>
-<a name="SEC_Top"></a>
<table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Cover (top) of
document">Top</a>]</td>
-<td valign="middle" align="left">[<a href="microhttpd_toc.html#SEC_Contents"
title="Table of contents">Contents</a>]</td>
-<td valign="middle" align="left">[<a href="microhttpd_22.html#SEC27"
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="microhttpd_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
</tr></table>
-<hr size="1">
+<a name="The-GNU-libmicrohttpd-Library"></a>
<h1 class="settitle">The GNU libmicrohttpd Library</h1>
-<p>This manual documents GNU libmicrohttpd version 0.4.2, last
-updated 11 October 2009. It is built upon the documentation in the
+<p>This manual documents GNU libmicrohttpd version 0.4.4, last
+updated 4 December 2009. It is built upon the documentation in the
header file ‘<tt>microhttpd.h</tt>’.
</p>
@@ -84,51 +83,3730 @@
<p>GNU libmicrohttpd is a GNU package.
</p>
<table class="menu" border="0" cellspacing="0">
-<tr><td align="left" valign="top"><a href="microhttpd_1.html#SEC1">1.
Introduction</a></td><td> </td><td align="left"
valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_2.html#SEC2">2.
Constants</a></td><td> </td><td align="left" valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_3.html#SEC3">3.
Structures type definition</a></td><td> </td><td align="left"
valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_4.html#SEC4">4. Callback
functions definition</a></td><td> </td><td align="left"
valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_5.html#SEC5">5. Starting
and stopping the server</a></td><td> </td><td align="left"
valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_6.html#SEC6">6.
Implementing external <code>select</code></a></td><td> </td><td
align="left" valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_7.html#SEC7">7. Handling
requests</a></td><td> </td><td align="left" valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_8.html#SEC8">8. Building
answers to responses</a></td><td> </td><td align="left"
valign="top"> Building responses to requests.
+<tr><td align="left" valign="top"><a href="#microhttpd_002dintro">1.
Introduction</a></td><td> </td><td align="left"
valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dconst">2.
Constants</a></td><td> </td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dstruct">3.
Structures type definition</a></td><td> </td><td align="left"
valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dcb">4. Callback
functions definition</a></td><td> </td><td align="left"
valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dinit">5. Starting
and stopping the server</a></td><td> </td><td align="left"
valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dinspect">6.
Implementing external <code>select</code></a></td><td> </td><td
align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002drequests">7.
Handling requests</a></td><td> </td><td align="left"
valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dresponses">8.
Building answers to responses</a></td><td> </td><td align="left"
valign="top"> Building responses to requests.
</td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_13.html#SEC13">9. Adding
a <code>POST</code> processor</a></td><td> </td><td align="left"
valign="top"></td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_15.html#SEC15">10.
Obtaining status information.</a></td><td> </td><td align="left"
valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dpost">9. Adding a
<code>POST</code> processor</a></td><td> </td><td align="left"
valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dinfo">10. Obtaining
status information.</a></td><td> </td><td align="left"
valign="top"></td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Appendices
-</pre></th></tr><tr><td align="left" valign="top"><a
href="microhttpd_18.html#SEC18">GNU-LGPL</a></td><td> </td><td
align="left" valign="top"> The GNU Lesser General Public
License says how you
- can copy and share almost all of
`libmicrohttpd'.
+</pre></th></tr><tr><td align="left" valign="top"><a
href="#GNU_002dLGPL">GNU-LGPL</a></td><td> </td><td align="left"
valign="top"> The GNU Lesser General Public License says
how you
+ can copy and share almost all of
‘libmicrohttpd’.
</td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_19.html#SEC22">GNU GPL
with eCos Extension</a></td><td> </td><td align="left" valign="top">
The GNU General Public License with eCos extension says how you
- can copy and share some parts of
`libmicrohttpd'.
+<tr><td align="left" valign="top"><a href="#GNU-GPL-with-eCos-Extension">GNU
GPL with eCos Extension</a></td><td> </td><td align="left"
valign="top"> The GNU General Public License with eCos extension says how you
+ can copy and share some parts of
‘libmicrohttpd’.
</td></tr>
-<tr><td align="left" valign="top"><a
href="microhttpd_21.html#SEC25">GNU-FDL</a></td><td> </td><td
align="left" valign="top"> The GNU Free Documentation
License says how you
- can copy and share the documentation of
`libmicrohttpd'.
+<tr><td align="left" valign="top"><a
href="#GNU_002dFDL">GNU-FDL</a></td><td> </td><td align="left"
valign="top"> The GNU Free Documentation License says how
you
+ can copy and share the documentation of
‘libmicrohttpd’.
</td></tr>
<tr><th colspan="3" align="left" valign="top"><pre class="menu-comment">
Indices
-</pre></th></tr><tr><td align="left" valign="top"><a
href="microhttpd_22.html#SEC27">Concept Index</a></td><td> </td><td
align="left" valign="top"> Index of concepts and programs.
+</pre></th></tr><tr><td align="left" valign="top"><a
href="#Concept-Index">Concept Index</a></td><td> </td><td
align="left" valign="top"> Index of concepts and programs.
</td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_23.html#SEC28">Function
and Data Index</a></td><td> </td><td align="left" valign="top">
Index of functions, variables and data types.
+<tr><td align="left" valign="top"><a href="#Function-and-Data-Index">Function
and Data Index</a></td><td> </td><td align="left" valign="top">
Index of functions, variables and data types.
</td></tr>
-<tr><td align="left" valign="top"><a href="microhttpd_24.html#SEC29">Type
Index</a></td><td> </td><td align="left" valign="top">
Index of data types.
+<tr><td align="left" valign="top"><a href="#Type-Index">Type
Index</a></td><td> </td><td align="left" valign="top">
Index of data types.
</td></tr>
</table>
<hr size="1">
+<a name="microhttpd_002dintro"></a>
<table cellpadding="1" cellspacing="1" border="0">
-<tr><td valign="middle" align="left">[<a href="#SEC_Top" title="Cover (top) of
document">Top</a>]</td>
-<td valign="middle" align="left">[<a href="microhttpd_toc.html#SEC_Contents"
title="Table of contents">Contents</a>]</td>
-<td valign="middle" align="left">[<a href="microhttpd_22.html#SEC27"
title="Index">Index</a>]</td>
-<td valign="middle" align="left">[<a href="microhttpd_abt.html#SEC_About"
title="About (help)"> ? </a>]</td>
+<tr><td valign="middle" align="left">[<a href="#Top" title="Previous section
in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dconst" title="Next
section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Beginning of this
chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dconst" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
</tr></table>
+<a name="Introduction"></a>
+<h1 class="chapter">1. Introduction</h1>
+
+
+<p>All symbols defined in the public <acronym>API</acronym> start with
<code>MHD_</code>. <acronym>MHD</acronym>
+is a small <acronym>HTTP</acronym> daemon library. As such, it does not have
any <acronym>API</acronym>
+for logging errors (you can only enable or disable logging to stderr).
+Also, it may not support all of the <acronym>HTTP</acronym> features directly,
where
+applicable, portions of <acronym>HTTP</acronym> may have to be handled by
clients of the
+library.
+</p>
+<p>The library is supposed to handle everything that it must handle
+(because the <acronym>API</acronym> would not allow clients to do this), such
as basic
+connection management; however, detailed interpretations of headers —
+such as range requests — and <acronym>HTTP</acronym> methods are left to
clients. The
+library does understand <code>HEAD</code> and will only send the headers of
+the response and not the body, even if the client supplied a body. The
+library also understands headers that control connection management
+(specifically, <code>Connection: close</code> and <code>Expect: 100
continue</code>
+are understood and handled automatically).
+</p>
+<p><acronym>MHD</acronym> understands <code>POST</code> data and is able to
decode certain
+formats (at the moment only <code>application/x-www-form-urlencoded</code>
+and <code>multipart/form-data</code>) using the post processor API. The
+data stream of a POST is also provided directly to the main
+application, so unsupported encodings could still be processed, just
+not conveniently by <acronym>MHD</acronym>.
+</p>
+<p>The header file defines various constants used by the
<acronym>HTTP</acronym> protocol.
+This does not mean that <acronym>MHD</acronym> actually interprets all of
these values.
+The provided constants are exported as a convenience for users of the
+library. <acronym>MHD</acronym> does not verify that transmitted
<acronym>HTTP</acronym> headers are
+part of the standard specification; users of the library are free to
+define their own extensions of the <acronym>HTTP</acronym> standard and use
those with
+<acronym>MHD</acronym>.
+</p>
+<p>All functions are guaranteed to be completely reentrant and
+thread-safe. <acronym>MHD</acronym> checks for allocation failures and tries
to
+recover gracefully (for example, by closing the connection).
+Additionally, clients can specify resource limits on the overall
+number of connections, number of connections per IP address and memory
+used per connection to avoid resource exhaustion.
+</p>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dconst"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dintro"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dstruct" title="Next
section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dintro"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dstruct" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Constants"></a>
+<h1 class="chapter">2. Constants</h1>
+
+
+<dl>
+<dt><a name="index-MHD_005fFLAG"></a><u>Enumeration:</u> <b>MHD_FLAG</b></dt>
+<dd><p>Options for the <acronym>MHD</acronym> daemon.
+</p>
+<p>Note that if neither <code>MHD_USER_THREAD_PER_CONNECTION</code> nor
+<code>MHD_USE_SELECT_INTERNALLY</code> are used, the client wants control over
+the process and will call the appropriate microhttpd callbacks.
+</p>
+<p>Starting the daemon may also fail if a particular option is not
+implemented or not supported on the target platform (i.e. no support for
+<acronym>SSL</acronym>, threads or IPv6). SSL support generally depends on
+options given during <acronym>MHD</acronym> compilation. Threaded operations
+(including <code>MHD_USE_SELECT_INTERNALLY</code>) are not supported on
+Symbian.
+</p>
+<dl compact="compact">
+<dt> <code>MHD_NO_FLAG</code></dt>
+<dd><p>No options selected.
+</p>
+</dd>
+<dt> <code>MHD_USE_DEBUG</code></dt>
+<dd><a name="index-debugging"></a>
+<p>Run in debug mode. If this flag is used, the library should print error
+messages and warnings to stderr. Note that <acronym>MHD</acronym> also needs
to be
+compiled with the configure option <code>--enable-messages</code> for this
+run-time option to have any effect.
+</p>
+</dd>
+<dt> <code>MHD_USE_SSL</code></dt>
+<dd><p>Run in https mode (this option may not work with all threading modes
yet).
+</p>
+</dd>
+<dt> <code>MHD_USE_THREAD_PER_CONNECTION</code></dt>
+<dd><p>Run using one thread per connection.
+</p>
+</dd>
+<dt> <code>MHD_USE_SELECT_INTERNALLY</code></dt>
+<dd><p>Run using an internal thread doing <code>SELECT</code>.
+</p>
+</dd>
+<dt> <code>MHD_USE_IPv6</code></dt>
+<dd><a name="index-IPv6"></a>
+<p>Run using the IPv6 protocol (otherwise, <acronym>MHD</acronym> will just
support IPv4).
+</p>
+
+</dd>
+<dt> <code>MHD_USE_PEDANTIC_CHECKS</code></dt>
+<dd><p>Be pedantic about the protocol (as opposed to as tolerant as possible).
+Specifically, at the moment, this flag causes <acronym>MHD</acronym> to reject
<acronym>HTTP</acronym>
+1.1 connections without a <code>Host</code> header. This is required by the
+standard, but of course in violation of the “be as liberal as possible
+in what you accept” norm. It is recommended to turn this
<strong>ON</strong>
+if you are testing clients against <acronym>MHD</acronym>, and
<strong>OFF</strong> in
+production.
+</p>
+</dd>
+<dt> <code>MHD_USE_POLL</code></dt>
+<dd><a name="index-FD_005fSETSIZE"></a>
+<a name="index-poll"></a>
+<a name="index-select"></a>
+<p>Use poll instead of select. This allows sockets with descriptors
+<code>>= FD_SETSIZE</code>. This option only works in conjunction with
+<code>MHD_USE_THREAD_PER_CONNECTION</code> (at this point).
+</p>
+</dd>
+</dl>
+</dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fOPTION"></a><u>Enumeration:</u>
<b>MHD_OPTION</b></dt>
+<dd><p><acronym>MHD</acronym> options. Passed in the varargs portion of
+<code>MHD_start_daemon()</code>.
+</p>
+<dl compact="compact">
+<dt> <code>MHD_OPTION_END</code></dt>
+<dd><p>No more options / last option. This is used to terminate the VARARGs
+list.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_CONNECTION_MEMORY_LIMIT</code></dt>
+<dd><a name="index-memory_002c-limiting-memory-utilization"></a>
+<p>Maximum memory size per connection (followed by a <code>size_t</code>). The
+default is 32 kB (32*1024 bytes) as defined by the internal constant
+<code>MHD_POOL_SIZE_DEFAULT</code>.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_CONNECTION_LIMIT</code></dt>
+<dd><a name="index-connection_002c-limiting-number-of-connections"></a>
+<p>Maximum number of concurrenct connections to accept (followed by an
+<code>unsigned int</code>). The default is <code>FD_SETSIZE - 4</code> (the
+maximum number of file descriptors supported by <code>select</code> minus
+four for <code>stdin</code>, <code>stdout</code>, <code>stderr</code> and the
server
+socket). In other words, the default is as large as possible.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_CONNECTION_TIMEOUT</code></dt>
+<dd><a name="index-timeout"></a>
+<p>After how many seconds of inactivity should a connection automatically
+be timed out? (followed by an <code>unsigned int</code>; use zero for no
+timeout). The default is zero (no timeout).
+</p>
+</dd>
+<dt> <code>MHD_OPTION_NOTIFY_COMPLETED</code></dt>
+<dd><p>Register a function that should be called whenever a request has been
+completed (this can be used for application-specific clean up).
+Requests that have never been presented to the application (via
+<code>MHD_AccessHandlerCallback()</code>) will not result in
+notifications.
+</p>
+<p>This option should be followed by <strong>TWO</strong> pointers. First a
+pointer to a function of type <code>MHD_RequestCompletedCallback()</code>
+and second a pointer to a closure to pass to the request completed
+callback. The second pointer maybe <code>NULL</code>.
+</p>
+
+</dd>
+<dt> <code>MHD_OPTION_PER_IP_CONNECTION_LIMIT</code></dt>
+<dd><p>Limit on the number of (concurrent) connections made to the
+server from the same IP address. Can be used to prevent one
+IP from taking over all of the allowed connections. If the
+same IP tries to establish more than the specified number of
+connections, they will be immediately rejected. The option
+should be followed by an <code>unsigned int</code>. The default is
+zero, which means no limit on the number of connections
+from the same IP address.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_SOCK_ADDR</code></dt>
+<dd><a name="index-bind_002c-restricting-bind"></a>
+<p>Bind daemon to the supplied socket address. This option should be followed
by a
+<code>struct sockaddr *</code>. If <code>MHD_USE_IPv6</code> is specified,
+the <code>struct sockaddr*</code> should point to a <code>struct
sockaddr_in6</code>,
+otherwise to a <code>struct sockaddr_in</code>. If this option is not
specified,
+the daemon will listen to incomming connections from anywhere.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_URI_LOG_CALLBACK</code></dt>
+<dd><a name="index-debugging-1"></a>
+<a name="index-logging"></a>
+<a name="index-query-string"></a>
+<p>Specify a function that should be called before parsing the URI from
+the client. The specified callback function can be used for processing
+the URI (including the options) before it is parsed. The URI after
+parsing will no longer contain the options, which maybe inconvenient for
+logging. This option should be followed by two arguments, the first
+one must be of the form
+</p><table><tr><td> </td><td><pre class="example"> void * my_logger(void
* cls, const char * uri)
+</pre></td></tr></table>
+<p>where the return value will be passed as
+<code>*con_cls</code> in calls to the <code>MHD_AccessHandlerCallback</code>
+when this request is processed later; returning a
+value of NULL has no special significance; (however,
+note that if you return non-NULL, you can no longer
+rely on the first call to the access handler having
+<code>NULL == *con_cls on entry</code> on entry)
+<code>cls</code> will be set to the second argument following
+MHD_OPTION_URI_LOG_CALLBACK. Finally, <code>uri</code> will
+be the 0-terminated URI of the request.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_HTTPS_MEM_KEY</code></dt>
+<dd><p>Memory pointer to the private key to be used by the
+HTTPS daemon. This option should be followed by an
+"const char*" argument.
+This should be used in conjunction with
’MHD_OPTION_HTTPS_MEM_CERT’.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_HTTPS_MEM_CERT</code></dt>
+<dd><p>Memory pointer to the certificate to be used by the
+HTTPS daemon. This option should be followed by an
+"const char*" argument.
+This should be used in conjunction with ’MHD_OPTION_HTTPS_MEM_KEY’.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_CRED_TYPE</code></dt>
+<dd><p>Daemon credentials type. Either certificate or anonymous,
+this option should be followed by one of the values listed in
+"enum MHD_GNUTLS_CredentialsType".
+</p>
+</dd>
+<dt> <code>MHD_OPTION_PROTOCOL_VERSION</code></dt>
+<dd><p>SSL/TLS protocol version.
+Memory pointer to a zero (MHD_GNUTLS_PROTOCOL_END) terminated
+(const) array of ’enum MHD_GNUTLS_Protocol’ values representing the
+protocol versions to this server should support. Unsupported
+requests will be dropped by the server.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_CIPHER_ALGORITHM</code></dt>
+<dd><p>Memory pointer to a zero (MHD_GNUTLS_CIPHER_UNKNOWN)
+terminated (const) array of ’enum MHD_GNUTLS_CipherAlgorithm’
+representing the cipher priority order to which the HTTPS
+daemon should adhere.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_EXTERNAL_LOGGER</code></dt>
+<dd><a name="index-logging-1"></a>
+<p>Use the given function for logging error messages.
+This option must be followed by two arguments; the
+first must be a pointer to a function
+of type ’void fun(void * arg, const char * fmt, va_list ap)’
+and the second a pointer of type ’void*’ which will
+be passed as the "arg" argument to "fun".
+</p>
+<p>Note that MHD will not generate any log messages
+if it was compiled without the "–enable-messages"
+flag being set and the MHD_USE_DEBUG flag being set,
+even if this argument is used.
+</p>
+</dd>
+<dt> <code>MHD_OPTION_ARRAY</code></dt>
+<dd><a name="index-options"></a>
+<p>This option can be used for initializing MHD using options from an
+array. A common use for this is writing an FFI for MHD. The actual
+options given are in an array of ’struct MHD_OptionItem’, so this
+option requires a single argument of type ’struct MHD_OptionItem’.
+The array must be terminated with an entry <code>MHD_OPTION_END</code>.
+</p>
+<p>An example for code using MHD_OPTION_ARRAY is:
+</p><table><tr><td> </td><td><pre class="example">struct MHD_OptionItem
ops[] = {
+ { MHD_OPTION_CONNECTION_LIMIT, 100, NULL },
+ { MHD_OPTION_CONNECTION_TIMEOUT, 10, NULL },
+ { MHD_OPTION_END, 0, NULL }
+};
+d = MHD_start_daemon(0, 8080, NULL, NULL, dh, NULL,
+ MHD_OPTION_ARRAY, ops,
+ MHD_OPTION_END);
+</pre></td></tr></table>
+<p>For options that expect a single pointer argument, the
+second member of the <code>struct MHD_OptionItem</code> is ignored.
+For options that expect two pointer arguments, the first
+argument must be cast to <code>intptr_t</code>.
+</p></dd>
+</dl>
+</dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fOptionItem"></a><u>C Struct:</u>
<b>MHD_OptionItem</b></dt>
+<dd><p>Entry in an MHD_OPTION_ARRAY. See the <code>MHD_OPTION_ARRAY</code>
option
+argument for its use.
+</p>
+<p>The <code>option</code> member is used to specify which option is specified
+in the array. The other members specify the respective argument.
+</p>
+<p>Note that for options taking only a single pointer, the
+<code>ptr_value</code> member should be set. For options taking two pointer
+arguments, the first pointer must be cast to <code>intptr_t</code> and both
+the <code>value</code> and the <code>ptr_value</code> members should be used to
+pass the two pointers.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fValueKind"></a><u>Enumeration:</u>
<b>MHD_ValueKind</b></dt>
+<dd><p>The <code>MHD_ValueKind</code> specifies the source of the key-value
pairs in
+the <acronym>HTTP</acronym> protocol.
+</p>
+<dl compact="compact">
+<dt> <code>MHD_RESPONSE_HEADER_KIND</code></dt>
+<dd><p>Response header.
+</p>
+</dd>
+<dt> <code>MHD_HEADER_KIND</code></dt>
+<dd><p><acronym>HTTP</acronym> header.
+</p>
+</dd>
+<dt> <code>MHD_COOKIE_KIND</code></dt>
+<dd><a name="index-cookie"></a>
+<p>Cookies. Note that the original <acronym>HTTP</acronym> header containing
the cookie(s)
+will still be available and intact.
+</p>
+</dd>
+<dt> <code>MHD_POSTDATA_KIND</code></dt>
+<dd><a name="index-POST-method"></a>
+<p><code>POST</code> data. This is available only if a content encoding
+supported by <acronym>MHD</acronym> is used (currently only
<acronym>URL</acronym> encoding), and
+only if the posted content fits within the available memory pool. Note
+that in that case, the upload data given to the
+<code>MHD_AccessHandlerCallback()</code> will be empty (since it has
+already been processed).
+</p>
+</dd>
+<dt> <code>MHD_GET_ARGUMENT_KIND</code></dt>
+<dd><p><code>GET</code> (<acronym>URI</acronym>) arguments.
+</p>
+</dd>
+<dt> <code>MHD_HEADER_KIND</code></dt>
+<dd><p><acronym>HTTP</acronym> footer (only for http 1.1 chunked encodings).
+</p>
+</dd>
+</dl>
+</dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fRequestTerminationCode"></a><u>Enumeration:</u>
<b>MHD_RequestTerminationCode</b></dt>
+<dd><p>The <code>MHD_RequestTerminationCode</code> specifies reasons why a
request
+has been terminated (or completed).
+</p>
+<dl compact="compact">
+<dt> <code>MHD_REQUEST_TERMINATED_COMPLETED_OK</code></dt>
+<dd><p>We finished sending the response.
+</p>
+</dd>
+<dt> <code>MHD_REQUEST_TERMINATED_WITH_ERROR</code></dt>
+<dd><p>Error handling the connection (resources exhausted, other side closed
+connection, application error accepting request, etc.)
+</p>
+</dd>
+<dt> <code>MHD_REQUEST_TERMINATED_TIMEOUT_REACHED</code></dt>
+<dd><p>No activity on the connection for the number of seconds specified using
+<code>MHD_OPTION_CONNECTION_TIMEOUT</code>.
+</p>
+</dd>
+<dt> <code>MHD_REQUEST_TERMINATED_DAEMON_SHUTDOWN</code></dt>
+<dd><p>We had to close the session since <acronym>MHD</acronym> was being shut
down.
+</p></dd>
+</dl>
+</dd></dl>
+
+<dl>
+<dt><a name="index-MHD_005fGNUTLS_005fProtocol"></a><u>Enumeration:</u>
<b>MHD_GNUTLS_Protocol</b></dt>
+<dd><p>SSL/TLS Protocol types. Note that not all listed algorithms are
+necessarily supported by all builds of MHD.
+</p>
+<dl compact="compact">
+<dt> <code>MHD_GNUTLS_PROTOCOL_END</code></dt>
+<dt> <code>MHD_GNUTLS_PROTOCOL_SSL3</code></dt>
+<dt> <code>MHD_GNUTLS_PROTOCOL_TLS1_0</code></dt>
+<dt> <code>MHD_GNUTLS_PROTOCOL_TLS1_1</code></dt>
+<dt> <code>MHD_GNUTLS_PROTOCOL_TLS1_2</code></dt>
+<dt> <code>MHD_GNUTLS_PROTOCOL_UNKNOWN</code></dt>
+</dl>
+</dd></dl>
+
+
+
+<dl>
+<dt><a name="index-MHD_005fGNUTLS_005fCipherAlgorithm"></a><u>Enumeration:</u>
<b>MHD_GNUTLS_CipherAlgorithm</b></dt>
+<dd><p>List of symmetric ciphers.
+Note that not all listed algorithms are necessarily supported by
+all builds of MHD.
+</p>
+<dl compact="compact">
+<dt> <code>MHD_GNUTLS_CIPHER_UNKNOWN</code></dt>
+<dt> <code>MHD_GNUTLS_CIPHER_NULL</code></dt>
+<dt> <code>MHD_GNUTLS_CIPHER_ARCFOUR_128</code></dt>
+<dt> <code>MHD_GNUTLS_CIPHER_3DES_CBC</code></dt>
+<dt> <code>MHD_GNUTLS_CIPHER_AES_128_CBC</code></dt>
+<dt> <code>MHD_GNUTLS_CIPHER_AES_256_CBC</code></dt>
+</dl>
+</dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fConnectionInfoType"></a><u>Enumeration:</u>
<b>MHD_ConnectionInfoType</b></dt>
+<dd><p>Values of this enum are used to specify what information about a
+connection is desired.
+</p>
+<dl compact="compact">
+<dt> <code>MHD_CONNECTION_INFO_CIPHER_ALGO</code></dt>
+<dd><p>What cipher algorithm is being used.
+Takes no extra arguments.
+</p>
+</dd>
+<dt> <code>MHD_CONNECTION_INFO_PROTOCOL,</code></dt>
+<dd><p>Takes no extra arguments.
+</p>
+</dd>
+</dl>
+</dd></dl>
+
+
+
+
+<dl>
+<dt><a name="index-MHD_005fDaemonInfoType"></a><u>Enumeration:</u>
<b>MHD_DaemonInfoType</b></dt>
+<dd><p>Values of this enum are used to specify what
+information about a deamon is desired.
+</p><dl compact="compact">
+<dt> <code>MHD_DAEMON_INFO_KEY_SIZE</code></dt>
+<dd><p>Request information about the key size for a particular cipher
+algorithm. The cipher algorithm should be passed as an extra argument
+(of type ’enum MHD_GNUTLS_CipherAlgorithm’).
+</p>
+</dd>
+<dt> <code>MHD_DAEMON_INFO_MAC_KEY_SIZE</code></dt>
+<dd><p>Request information about the key size for a particular cipher
+algorithm. The cipher algorithm should be passed as an extra argument
+(of type ’enum MHD_GNUTLS_HashAlgorithm’).
+</p>
+</dd>
+<dt> <code>MHD_DAEMON_INFO_LISTEN_FD</code></dt>
+<dd><a name="index-listen"></a>
+<p>Request the file-descriptor number that MHD is using to listen to the
+server socket. This can be useful if no port
+was specified and a client needs to learn what port
+is actually being used by MHD.
+No extra arguments should be passed.
+</p>
+</dd>
+</dl>
+</dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dstruct"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dconst"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dcb" title="Next
section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dconst"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dcb" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Structures-type-definition"></a>
+<h1 class="chapter">3. Structures type definition</h1>
+
+
+<dl>
+<dt><a name="index-MHD_005fDaemon"></a><u>C Struct:</u> <b>MHD_Daemon</b></dt>
+<dd><p>Handle for the daemon (listening on a socket for
<acronym>HTTP</acronym> traffic).
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fConnection"></a><u>C Struct:</u>
<b>MHD_Connection</b></dt>
+<dd><p>Handle for a connection / <acronym>HTTP</acronym> request. With
<acronym>HTTP</acronym>/1.1, multiple
+requests can be run over the same connection. However, <acronym>MHD</acronym>
will only
+show one request per <acronym>TCP</acronym> connection to the client at any
given time.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fResponse"></a><u>C Struct:</u>
<b>MHD_Response</b></dt>
+<dd><p>Handle for a response.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fPostProcessor"></a><u>C Struct:</u>
<b>MHD_PostProcessor</b></dt>
+<dd><a name="index-POST-method-1"></a>
+<p>Handle for <code>POST</code> processing.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fConnectionInfo"></a><u>C Union:</u>
<b>MHD_ConnectionInfo</b></dt>
+<dd><p>Information about a connection.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fDaemonInfo"></a><u>C Union:</u>
<b>MHD_DaemonInfo</b></dt>
+<dd><p>Information about an MHD daemon.
+</p></dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dcb"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dstruct"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinit" title="Next
section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dstruct"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinit" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Callback-functions-definition"></a>
+<h1 class="chapter">4. Callback functions definition</h1>
+
+
+<dl>
+<dt><a name="index-_002aMHD_005fAcceptPolicyCallback"></a><u>Function
Pointer:</u> int <b>*MHD_AcceptPolicyCallback</b><i> (void *cls, const struct
sockaddr * addr, socklen_t addrlen)</i></dt>
+<dd><p>Invoked in the context of a connection to allow or deny a client to
+connect. This callback return <code>MHD_YES</code> if connection is allowed,
+<code>MHD_NO</code> if not.
+</p>
+<dl compact="compact">
+<dt> <var>cls</var></dt>
+<dd><p>custom value selected at callback registration time;
+</p></dd>
+<dt> <var>addr</var></dt>
+<dd><p>address information from the client;
+</p></dd>
+<dt> <var>addrlen</var></dt>
+<dd><p>length of the address information.
+</p></dd>
+</dl>
+</dd></dl>
+
+
+<dl>
+<dt><a name="index-_002aMHD_005fAccessHandlerCallback"></a><u>Function
Pointer:</u> int <b>*MHD_AccessHandlerCallback</b><i> (void *cls, struct
MHD_Connection * connection, const char *url, const char *method, const char
*version, const char *upload_data, size_t *upload_data_size, void
**con_cls)</i></dt>
+<dd><p>Invoked in the context of a connection to answer a request from the
+client. This callback must call <acronym>MHD</acronym> functions (example: the
+<code>MHD_Response</code> ones) to provide content to give back to the client
+and return an <acronym>HTTP</acronym> status code (i.e. <code>200</code> for
OK, <code>404</code>,
+etc.).
+</p>
+<p><a href="#microhttpd_002dpost">Adding a <code>POST</code> processor</a>,
for details on how to code this callback.
+</p>
+<p>Must return <code>MHD_YES</code> if the connection was handled successfully,
+<code>MHD_NO</code> if the socket must be closed due to a serious error while
+handling the request
+</p>
+<dl compact="compact">
+<dt> <var>cls</var></dt>
+<dd><p>custom value selected at callback registration time;
+</p>
+</dd>
+<dt> <var>url</var></dt>
+<dd><p>the <acronym>URL</acronym> requested by the client;
+</p>
+</dd>
+<dt> <var>method</var></dt>
+<dd><p>the <acronym>HTTP</acronym> method used by the client
(<code>GET</code>, <code>PUT</code>,
+<code>DELETE</code>, <code>POST</code>, etc.);
+</p>
+</dd>
+<dt> <var>version</var></dt>
+<dd><p>the <acronym>HTTP</acronym> version string (i.e. <code>HTTP/1.1</code>);
+</p>
+</dd>
+<dt> <var>upload_data</var></dt>
+<dd><p>the data being uploaded (excluding headers):
+<a name="index-POST-method-2"></a>
+<a name="index-PUT-method"></a>
+</p>
+<ul>
+<li>
+for a <code>POST</code> that fits into memory and that is encoded with a
+supported encoding, the <code>POST</code> data will <strong>NOT</strong> be
given in
+<var>upload_data</var> and is instead available as part of
+<code>MHD_get_connection_values()</code>;
+
+</li><li>
+very large <code>POST</code> data <strong>will</strong> be made available
+incrementally in <var>upload_data</var>;
+</li></ul>
+
+</dd>
+<dt> <var>upload_data_size</var></dt>
+<dd><p>set initially to the size of the <var>upload_data</var> provided; this
+callback must update this value to the number of bytes <strong>NOT</strong>
+processed; unless external select is used, the callback maybe
+required to process at least some data. If the callback fails to
+process data in multi-threaded or internal-select mode and if the
+read-buffer is already at the maximum size that MHD is willing to
+use for reading (about half of the maximum amount of memory allowed
+for the connection), then MHD will abort handling the connection
+and return an internal server error to the client. In order to
+avoid this, clients must be able to process upload data incrementally
+and reduce the value of <code>upload_data_size</code>.
+</p>
+</dd>
+<dt> <var>con_cls</var></dt>
+<dd><p>reference to a pointer, initially set to <code>NULL</code>, that this
callback can
+set to some address and that will be preserved by <acronym>MHD</acronym> for
future
+calls for this request;
+</p>
+<p>since the access handler may be called many times (i.e., for a
+<code>PUT</code>/<code>POST</code> operation with plenty of upload data) this
allows
+the application to easily associate some request-specific state;
+</p>
+<p>if necessary, this state can be cleaned up in the global
+<code>MHD_RequestCompletedCallback</code> (which can be set with the
+<code>MHD_OPTION_NOTIFY_COMPLETED</code>).
+</p></dd>
+</dl>
+</dd></dl>
+
+
+<dl>
+<dt><a name="index-_002aMHD_005fRequestCompletedCallback"></a><u>Function
Pointer:</u> void <b>*MHD_RequestCompletedCallback</b><i> (void *cls, struct
MHD_Connectionconnection, void **con_cls, enum MHD_RequestTerminationCode
toe)</i></dt>
+<dd><p>Signature of the callback used by <acronym>MHD</acronym> to notify the
application about
+completed requests.
+</p>
+<dl compact="compact">
+<dt> <var>cls</var></dt>
+<dd><p>custom value selected at callback registration time;
+</p>
+</dd>
+<dt> <var>connection</var></dt>
+<dd><p>connection handle;
+</p>
+</dd>
+<dt> <var>con_cls</var></dt>
+<dd><p>value as set by the last call to the
+<code>MHD_AccessHandlerCallback</code>;
+</p>
+</dd>
+<dt> <var>toe</var></dt>
+<dd><p>reason for request termination see
<code>MHD_OPTION_NOTIFY_COMPLETED</code>.
+</p></dd>
+</dl>
+</dd></dl>
+
+
+<dl>
+<dt><a name="index-_002aMHD_005fKeyValueIterator"></a><u>Function Pointer:</u>
int <b>*MHD_KeyValueIterator</b><i> (void *cls, enum MHD_ValueKind kind, const
char *key, const char *value)</i></dt>
+<dd><p>Iterator over key-value pairs. This iterator can be used to iterate
+over all of the cookies, headers, or <code>POST</code>-data fields of a
+request, and also to iterate over the headers that have been added to a
+response.
+</p>
+<p>Return <code>MHD_YES</code> to continue iterating, <code>MHD_NO</code> to
abort the
+iteration.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-_002aMHD_005fContentReaderCallback"></a><u>Function
Pointer:</u> int <b>*MHD_ContentReaderCallback</b><i> (void *cls, uint64_t pos,
char *buf, int max)</i></dt>
+<dd><p>Callback used by <acronym>MHD</acronym> in order to obtain content.
The callback has to
+copy at most <var>max</var> bytes of content into <var>buf</var>. The total
+number of bytes that has been placed into <var>buf</var> should be returned.
+</p>
+<p>Note that returning zero will cause <acronym>MHD</acronym> to try again,
either
+“immediately” if in multi-threaded mode (in which case the callback
+may want to do blocking operations to avoid busy waiting) or in the
+next round if <code>MHD_run</code> is used. Returning zero for a daemon
+that runs in internal <code>select()</code> mode is an error (since it
+would result in busy waiting) and cause the program to be aborted
+(<code>abort()</code>).
+</p>
+<dl compact="compact">
+<dt> <var>cls</var></dt>
+<dd><p>custom value selected at callback registration time;
+</p>
+</dd>
+<dt> <var>pos</var></dt>
+<dd><p>position in the datastream to access; note that if an
+<code>MHD_Response</code> object is re-used, it is possible for the same
+content reader to be queried multiple times for the same data; however,
+if an <code>MHD_Response</code> is not re-used, <acronym>MHD</acronym>
guarantees that
+<var>pos</var> will be the sum of all non-negative return values obtained
+from the content reader so far.
+</p></dd>
+</dl>
+
+<p>Return <code>-1</code> on error (<acronym>MHD</acronym> will no longer try
to read content and
+instead close the connection with the client).
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-_002aMHD_005fContentReaderFreeCallback"></a><u>Function
Pointer:</u> void <b>*MHD_ContentReaderFreeCallback</b><i> (void *cls)</i></dt>
+<dd><p>This method is called by <acronym>MHD</acronym> if we are done with a
content reader.
+It should be used to free resources associated with the content reader.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-_002aMHD_005fPostDataIterator"></a><u>Function Pointer:</u>
int <b>*MHD_PostDataIterator</b><i> (void *cls, enum MHD_ValueKind kind, const
char *key, const char *filename, const char *content_type, const char
*transfer_encoding, const char *data, uint64_t off, size_t size)</i></dt>
+<dd><p>Iterator over key-value pairs where the value maybe made available in
+increments and/or may not be zero-terminated. Used for processing
+<code>POST</code> data.
+</p>
+<dl compact="compact">
+<dt> <var>cls</var></dt>
+<dd><p>custom value selected at callback registration time;
+</p>
+</dd>
+<dt> <var>kind</var></dt>
+<dd><p>type of the value;
+</p>
+</dd>
+<dt> <var>key</var></dt>
+<dd><p>zero-terminated key for the value;
+</p>
+</dd>
+<dt> <var>filename</var></dt>
+<dd><p>name of the uploaded file, <code>NULL</code> if not known;
+</p>
+</dd>
+<dt> <var>content_type</var></dt>
+<dd><p>mime-type of the data, <code>NULL</code> if not known;
+</p>
+</dd>
+<dt> <var>transfer_encoding</var></dt>
+<dd><p>encoding of the data, <code>NULL</code> if not known;
+</p>
+</dd>
+<dt> <var>data</var></dt>
+<dd><p>pointer to size bytes of data at the specified offset;
+</p>
+</dd>
+<dt> <var>off</var></dt>
+<dd><p>offset of data in the overall value;
+</p>
+</dd>
+<dt> <var>size</var></dt>
+<dd><p>number of bytes in data available.
+</p></dd>
+</dl>
+
+<p>Return <code>MHD_YES</code> to continue iterating, <code>MHD_NO</code> to
abort the
+iteration.
+</p></dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dinit"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dcb"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinspect"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dcb"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinspect"
title="Next chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Starting-and-stopping-the-server"></a>
+<h1 class="chapter">5. Starting and stopping the server</h1>
+
+<dl>
+<dt><a name="index-MHD_005fset_005fpanic_005ffunc"></a><u>Function:</u> void
<b>MHD_set_panic_func</b><i> (MHD_PanicCallback cb, void *cls)</i></dt>
+<dd><p>Set a handler for fatal errors.
+</p>
+<dl compact="compact">
+<dt> <var>cb</var> </dt>
+<dd><p>function to call if MHD encounteres a fatal internal error. If no
handler was set explicitly, MHD will call <code>abort</code>.
+</p>
+</dd>
+<dt> <var>cls</var></dt>
+<dd><p>closure argument for cb; the other arguments are the name of the source
file, line number and a string describing the nature of the fatal error (which
can be NULL)
+</p></dd>
+</dl>
+</dd></dl>
+
+<dl>
+<dt><a name="index-MHD_005fstart_005fdaemon"></a><u>Function:</u> struct
MHD_Daemon * <b>MHD_start_daemon</b><i> (unsigned int flags, unsigned short
port, MHD_AcceptPolicyCallback apc, void *apc_cls, MHD_AccessHandlerCallback
dh, void *dh_cls, ...)</i></dt>
+<dd><p>Start a webserver on the given port.
+</p>
+<dl compact="compact">
+<dt> <var>flags</var></dt>
+<dd><p>OR-ed combination of <code>MHD_FLAG</code> values;
+</p>
+</dd>
+<dt> <var>port</var></dt>
+<dd><p>port to bind to;
+</p>
+</dd>
+<dt> <var>apc</var></dt>
+<dd><p>callback to call to check which clients will be allowed to connect; you
+can pass <code>NULL</code> in which case connections from any
<acronym>IP</acronym> will be
+accepted;
+</p>
+</dd>
+<dt> <var>apc_cls</var></dt>
+<dd><p>extra argument to <var>apc</var>;
+</p>
+</dd>
+<dt> <var>dh</var></dt>
+<dd><p>default handler for all <acronym>URI</acronym>s;
+</p>
+</dd>
+<dt> <var>dh_cls</var></dt>
+<dd><p>extra argument to <var>dh</var>.
+</p></dd>
+</dl>
+
+<p>Additional arguments are a list of options (type-value pairs,
+terminated with <code>MHD_OPTION_END</code>). It is mandatory to use
+<code>MHD_OPTION_END</code> as last argument, even when there are no
+additional arguments.
+</p>
+<p>Return <code>NULL</code> on error, handle to daemon on success.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fstop_005fdaemon"></a><u>Function:</u> void
<b>MHD_stop_daemon</b><i> (struct MHD_Daemon *daemon)</i></dt>
+<dd><p>Shutdown an <acronym>HTTP</acronym> daemon.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005frun"></a><u>Function:</u> int <b>MHD_run</b><i>
(struct MHD_Daemon *daemon)</i></dt>
+<dd><p>Run webserver operations (without blocking unless in client callbacks).
+This method should be called by clients in combination with
+<code>MHD_get_fdset()</code> if the client-controlled <code>select()</code>
+method is used.
+</p>
+<p>Return <code>MHD_YES</code> on success, <code>MHD_NO</code> if this daemon
was not
+started with the right options for this call.
+</p></dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dinspect"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dinit"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002drequests"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinit"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002drequests"
title="Next chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Implementing-external-select"></a>
+<h1 class="chapter">6. Implementing external <code>select</code></h1>
+
+
+<dl>
+<dt><a name="index-MHD_005fget_005ffdset"></a><u>Function:</u> int
<b>MHD_get_fdset</b><i> (struct MHD_Daemon *daemon, fd_set * read_fd_set,
fd_set * write_fd_set, fd_set * except_fd_set, int *max_fd)</i></dt>
+<dd><p>Obtain the <code>select()</code> sets for this daemon. The
daemon’s socket
+is added to <var>read_fd_set</var>. The list of currently existent
+connections is scanned and their file descriptors added to the correct
+set.
+</p>
+<p>see <a href="libc.html#Top">(libc)</a>, for details on file descriptor sets.
+</p>
+<p>After the call completed successfully: the variable referenced by
+<var>max_fd</var> references the file descriptor with highest integer
+identifier. The variable must be set to zero before invoking this
+function.
+</p>
+<p>Return <code>MHD_YES</code> on success, <code>MHD_NO</code> if: the
arguments are
+invalid (example: <code>NULL</code> pointers); this daemon was not started with
+the right options for this call.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fget_005ftimeout"></a><u>Function:</u> int
<b>MHD_get_timeout</b><i> (struct MHD_Daemon *daemon, unsigned long long
*timeout)</i></dt>
+<dd><a name="index-timeout-1"></a>
+<p>Obtain timeout value for select for this daemon (only needed if
+connection timeout is used). The returned value is how long
+<code>select()</code> should at most block, not the timeout value set for
+connections.
+</p>
+<dl compact="compact">
+<dd><a name="index-timeout-2"></a>
+<p>set to the timeout (in milliseconds).
+</p></dd>
+</dl>
+
+<p>Return <code>MHD_YES</code> on success, <code>MHD_NO</code> if timeouts are
not used
+(or no connections exist that would necessiate the use of a timeout
+right now).
+</p></dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002drequests"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dinspect"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinspect"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Next chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Handling-requests"></a>
+<h1 class="chapter">7. Handling requests</h1>
+
+
+<dl>
+<dt><a name="index-MHD_005fget_005fconnection_005fvalues"></a><u>Function:</u>
int <b>MHD_get_connection_values</b><i> (struct MHD_Connection *connection,
enum MHD_ValueKind kind, MHD_KeyValueIterator iterator, void
*iterator_cls)</i></dt>
+<dd><p>Get all the headers matching <var>kind</var> from the request.
+</p>
+<p>The <var>iterator</var> callback is invoked once for each header, with
+<var>iterator_cls</var> as first argument. Return the number of entries
+iterated over; this can be less than the number of headers if, while
+iterating, <var>iterator</var> returns <code>MHD_NO</code>.
+</p>
+<p><var>iterator</var> can be <code>NULL</code>: in this case this function
just counts
+and returns the number of headers.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fset_005fconnection_005fvalue"></a><u>Function:</u>
int <b>MHD_set_connection_value</b><i> (struct MHD_Connection *connection, enum
MHD_ValueKind kind, const char * key, const char * value)</i></dt>
+<dd><p>This function can be used to add an entry to
+the HTTP headers of a connection (so that the
+MHD_get_connection_values function will return
+them – and the MHD PostProcessor will also
+see them). This maybe required in certain
+situations (see Mantis #1399) where (broken)
+HTTP implementations fail to supply values needed
+by the post processor (or other parts of the
+application).
+</p>
+<p>This function MUST only be called from within
+the MHD_AccessHandlerCallback (otherwise, access
+maybe improperly synchronized). Furthermore,
+the client must guarantee that the key and
+value arguments are 0-terminated strings that
+are NOT freed until the connection is closed.
+(The easiest way to do this is by passing only
+arguments to permanently allocated strings.).
+</p>
+<p><var>connection</var> is the connection for which
+the entry for <var>key</var> of the given <var>kind</var>
+should be set to the given <var>value</var>.
+</p>
+<p>The function returns <code>MHD_NO</code> if the operation
+could not be performed due to insufficient memory
+and <code>MHD_YES</code> on success.
+</p></dd></dl>
+
+
+<dl>
+<dt><a
name="index-MHD_005flookup_005fconnection_005fvalue"></a><u>Function:</u> const
char * <b>MHD_lookup_connection_value</b><i> (struct MHD_Connection
*connection, enum MHD_ValueKind kind, const char *key)</i></dt>
+<dd><p>Get a particular header value. If multiple values match the
<var>kind</var>,
+return one of them (the “first”, whatever that means).
<var>key</var> must
+reference a zero-terminated <acronym>ASCII</acronym>-coded string representing
the
+header to look for: it is compared against the headers using
+<code>strcasecmp()</code>, so case is ignored. Return <code>NULL</code> if no
such
+item was found.
+</p></dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dresponses"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002drequests"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponse-enqueue"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002drequests"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Building-answers-to-responses"></a>
+<h1 class="chapter">8. Building answers to responses</h1>
+
+
+<p>Response objects handling by <acronym>MHD</acronym> is asynchronous with
respect to the
+application execution flow. Instances of the <code>MHD_Response</code>
+structure are not associated to a daemon and neither to a client
+connection: they are managed with reference counting.
+</p>
+<p>In the simplest case: we allocate a new <code>MHD_Response</code> structure
+for each response, we use it once and finally we destroy it.
+</p>
+<p><acronym>MHD</acronym> allows more efficient resources usages.
+</p>
+<p>Example: we allocate a new <code>MHD_Response</code> structure for each
+response <strong>kind</strong>, we use it every time we have to give that
+responce and we finally destroy it only when the daemon shuts down.
+</p>
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top"><a
href="#microhttpd_002dresponse-enqueue">8.1 Enqueuing a
response</a></td><td> </td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a
href="#microhttpd_002dresponse-create">8.2 Creating response
objects</a></td><td> </td><td align="left" valign="top"> Creating a
response object.
+</td></tr>
+<tr><td align="left" valign="top"><a
href="#microhttpd_002dresponse-headers">8.3 Adding headers to a
response</a></td><td> </td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a
href="#microhttpd_002dresponse-inspect">8.4 Inspecting a response
object</a></td><td> </td><td align="left" valign="top"></td></tr>
+</table>
+
+
+<hr size="6">
+<a name="microhttpd_002dresponse-enqueue"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponse-create"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Enqueuing-a-response"></a>
+<h2 class="section">8.1 Enqueuing a response</h2>
+
+
+<dl>
+<dt><a name="index-MHD_005fqueue_005fresponse"></a><u>Function:</u> int
<b>MHD_queue_response</b><i> (struct MHD_Connection *connection, unsigned int
status_code, struct MHD_Response *response)</i></dt>
+<dd><p>Queue a response to be transmitted to the client as soon as possible
+but only after MHD_AccessHandlerCallback returns. This function
+checks that it is legal to queue a response at this time for the
+given connection. It also increments the internal reference
+counter for the response object (the counter will be decremented
+automatically once the response has been transmitted).
+</p>
+<dl compact="compact">
+<dt> <var>connection</var></dt>
+<dd><p>the connection identifying the client;
+</p>
+</dd>
+<dt> <var>status_code</var></dt>
+<dd><p><acronym>HTTP</acronym> status code (i.e. <code>200</code> for OK);
+</p>
+</dd>
+<dt> <var>response</var></dt>
+<dd><p>response to transmit.
+</p></dd>
+</dl>
+
+<p>Return <code>MHD_YES</code> on success or if message has been queued.
Return
+<code>MHD_NO</code>: if arguments are invalid (example: <code>NULL</code>
pointer); on
+error (i.e. reply already sent).
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fdestroy_005fresponse"></a><u>Function:</u> void
<b>MHD_destroy_response</b><i> (struct MHD_Response *response)</i></dt>
+<dd><p>Destroy a response object and associated resources (decrement the
+reference counter). Note that <acronym>MHD</acronym> may keep some of the
resources
+around if the response is still in the queue for some clients, so the
+memory may not necessarily be freed immediatley.
+</p></dd></dl>
+
+
+<p>An explanation of reference counting<a name="DOCF1" href="#FOOT1">(1)</a>:
+</p>
+<ol>
+<li>
+a <code>MHD_Response</code> object is allocated:
+
+<table><tr><td> </td><td><pre class="example">struct MHD_Response *
response = MHD_create_response_from_data(...);
+/* here: reference counter = 1 */
+</pre></td></tr></table>
+
+</li><li>
+the <code>MHD_Response</code> object is enqueued in a
<code>MHD_Connection</code>:
+
+<table><tr><td> </td><td><pre
class="example">MHD_queue_response(connection, , response);
+/* here: reference counter = 2 */
+</pre></td></tr></table>
+
+</li><li>
+the creator of the response object discharges responsibility for it:
+
+<table><tr><td> </td><td><pre
class="example">MHD_destroy_response(response);
+/* here: reference counter = 1 */
+</pre></td></tr></table>
+
+</li><li>
+the daemon handles the connection sending the response’s data to the
+client then decrements the reference counter by calling
+<code>MHD_destroy_response()</code>: the counter’s value drops to zero
and
+the <code>MHD_Response</code> object is released.
+</li></ol>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dresponse-create"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a
href="#microhttpd_002dresponse-enqueue" title="Previous section in reading
order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponse-headers"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Creating-response-objects"></a>
+<h2 class="section">8.2 Creating response objects</h2>
+
+
+<dl>
+<dt><a
name="index-MHD_005fcreate_005fresponse_005ffrom_005fcallback"></a><u>Function:</u>
struct MHD_Response * <b>MHD_create_response_from_callback</b><i> (uint64_t
size, size_t block_size, MHD_ContentReaderCallback crc, void *crc_cls,
MHD_ContentReaderFreeCallback crfc)</i></dt>
+<dd><p>Create a response object. The response object can be extended with
+header information and then it can be used any number of times.
+</p>
+<dl compact="compact">
+<dt> <var>size</var></dt>
+<dd><p>size of the data portion of the response, <code>-1</code> for unknown;
+</p>
+</dd>
+<dt> <var>block_size</var></dt>
+<dd><p>preferred block size for querying <var>crc</var> (advisory only,
<acronym>MHD</acronym> may
+still call <var>crc</var> using smaller chunks); this is essentially the
+buffer size used for <acronym>IO</acronym>, clients should pick a value that is
+appropriate for <acronym>IO</acronym> and memory performance requirements;
+</p>
+</dd>
+<dt> <var>crc</var></dt>
+<dd><p>callback to use to obtain response data;
+</p>
+</dd>
+<dt> <var>crc_cls</var></dt>
+<dd><p>extra argument to <var>crc</var>;
+</p>
+</dd>
+<dt> <var>crfc</var></dt>
+<dd><p>callback to call to free <var>crc_cls</var> resources.
+</p></dd>
+</dl>
+
+<p>Return <code>NULL</code> on error (i.e. invalid arguments, out of memory).
+</p></dd></dl>
+
+
+<dl>
+<dt><a
name="index-MHD_005fcreate_005fresponse_005ffrom_005fdata"></a><u>Function:</u>
struct MHD_Response * <b>MHD_create_response_from_data</b><i> (size_t size,
void *data, int must_free, int must_copy)</i></dt>
+<dd><p>Create a response object. The response object can be extended with
+header information and then it can be used any number of times.
+</p>
+<dl compact="compact">
+<dt> <var>size</var></dt>
+<dd><p>size of the data portion of the response;
+</p>
+</dd>
+<dt> <var>data</var></dt>
+<dd><p>the data itself;
+</p>
+</dd>
+<dt> <var>must_free</var></dt>
+<dd><p>if true: <acronym>MHD</acronym> should free data when done;
+</p>
+</dd>
+<dt> <var>must_copy</var></dt>
+<dd><p>if true: <acronym>MHD</acronym> allocates a block of memory and use it
to make a copy of
+<var>data</var> embedded in the returned <code>MHD_Response</code> structure;
+handling of the embedded memory is responsibility of <acronym>MHD</acronym>;
<var>data</var>
+can be released anytime after this call returns.
+</p></dd>
+</dl>
+
+<p>Return <code>NULL</code> on error (i.e. invalid arguments, out of memory).
+</p></dd></dl>
+
+
+<p>Example: create a response from a statically allocated string:
+</p>
+<table><tr><td> </td><td><pre class="example">const char * data =
"<html><body><p>Error!</p></body></html>";
+
+struct MHD_Connection * connection = ...;
+struct MHD_Response * response;
+
+response = MHD_create_response_from_data(strlen(data), data,
+ MHD_NO, MHD_NO);
+MHD_queue_response(connection, 404, response);
+MHD_destroy_response(response);
+</pre></td></tr></table>
+
+
+
+
+<hr size="6">
+<a name="microhttpd_002dresponse-headers"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a
href="#microhttpd_002dresponse-create" title="Previous section in reading
order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponse-inspect"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Adding-headers-to-a-response"></a>
+<h2 class="section">8.3 Adding headers to a response</h2>
+
+
+<dl>
+<dt><a name="index-MHD_005fadd_005fresponse_005fheader"></a><u>Function:</u>
int <b>MHD_add_response_header</b><i> (struct MHD_Response *response, const
char *header, const char *content)</i></dt>
+<dd><p>Add a header line to the response. The strings referenced by
+<var>header</var> and <var>content</var> must be zero-terminated and they are
+duplicated into memory blocks embedded in <var>response</var>.
+</p>
+<p>Notice that the strings must not hold newlines, carriage returns or tab
+chars.
+</p>
+<p>Return <code>MHD_NO</code> on error (i.e. invalid header or content format
or
+memory allocation error).
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fdel_005fresponse_005fheader"></a><u>Function:</u>
int <b>MHD_del_response_header</b><i> (struct MHD_Response *response, const
char *header, const char *content)</i></dt>
+<dd><p>Delete a header line from the response. Return <code>MHD_NO</code> on
error
+(arguments are invalid or no such header known).
+</p></dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dresponse-inspect"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a
href="#microhttpd_002dresponse-headers" title="Previous section in reading
order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost" title="Next
section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Inspecting-a-response-object"></a>
+<h2 class="section">8.4 Inspecting a response object</h2>
+
+
+<dl>
+<dt><a name="index-MHD_005fget_005fresponse_005fheaders"></a><u>Function:</u>
int <b>MHD_get_response_headers</b><i> (struct MHD_Response *response,
MHD_KeyValueIterator iterator, void *iterator_cls)</i></dt>
+<dd><p>Get all of the headers added to a response.
+</p>
+<p>Invoke the <var>iterator</var> callback for each header in the response,
+using <var>iterator_cls</var> as first argument. Return number of entries
+iterated over. <var>iterator</var> can be <code>NULL</code>: in this case the
function
+just counts headers.
+</p>
+<p><var>iterator</var> should not modify the its key and value arguments,
unless
+we know what we are doing.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fget_005fresponse_005fheader"></a><u>Function:</u>
const char * <b>MHD_get_response_header</b><i> (struct MHD_Response *response,
const char *key)</i></dt>
+<dd><p>Find and return a pointer to the value of a particular header from the
+response. <var>key</var> must reference a zero-terminated string
+representing the header to look for. The search is case sensitive.
+Return <code>NULL</code> if header does not exist or <var>key</var> is
<code>NULL</code>.
+</p>
+<p>We should not modify the value, unless we know what we are doing.
+</p></dd></dl>
+
+
+
+<hr size="6">
+<a name="microhttpd_002dpost"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a
href="#microhttpd_002dresponse-inspect" title="Previous section in reading
order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost-api"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dresponses"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Adding-a-POST-processor"></a>
+<h1 class="chapter">9. Adding a <code>POST</code> processor</h1>
+<a name="index-POST-method-3"></a>
+
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top"><a href="#microhttpd_002dpost-api">9.1
Programming interface for the <code>POST</code>
processor</a></td><td> </td><td align="left" valign="top"></td></tr>
+</table>
+
+
+<p><acronym>MHD</acronym> provides the post procesor API to make it easier for
applications to
+parse the data of a client’s <code>POST</code> request: the
+<code>MHD_AccessHandlerCallback</code> will be invoked multiple times to
+process data as it arrives; at each invocation a new chunk of data must
+be processed. The arguments <var>upload_data</var> and
<var>upload_data_size</var>
+are used to reference the chunk of data.
+</p>
+<p>When <code>MHD_AccessHandlerCallback</code> is invoked for a new connection:
+its <code>*<var>con_cls</var></code> argument is set to <code>NULL</code>.
When <code>POST</code>
+data comes in the upload buffer it is <strong>mandatory</strong> to use the
+<var>con_cls</var> to store a reference to per-connection data. The fact
+that the pointer was initially <code>NULL</code> can be used to detect that
+this is a new request.
+</p>
+<p>One method to detect that a new connection was established is
+to set <code>*con_cls</code> to anunused integer:
+</p>
+<table><tr><td> </td><td><pre class="example">int
+access_handler (void *cls,
+ struct MHD_Connection * connection,
+ const char *url,
+ const char *method, const char *version,
+ const char *upload_data, size_t *upload_data_size,
+ void **con_cls)
+{
+ static int old_connection_marker;
+ int new_connection = (MYNULL == *con_cls);
+
+ if (new_connection)
+ {
+ /* new connection with POST */
+ *con_cls = &old_connection_marker;
+ }
+
+ ...
+}
+</pre></td></tr></table>
+
+<p>In contrast to the previous example, for <code>POST</code> requests in
particular,
+it is more common to use the value of <code>*con_cls</code> to keep track of
+actual state used during processing, such as the post processor (or a
+struct containing a post processor):
+</p>
+<table><tr><td> </td><td><pre class="example">int
+access_handler (void *cls,
+ struct MHD_Connection * connection,
+ const char *url,
+ const char *method, const char *version,
+ const char *upload_data, size_t *upload_data_size,
+ void **con_cls)
+{
+ struct MHD_PostProcessor * pp = *con_cls;
+
+ if (pp == NULL)
+ {
+ pp = MHD_create_post_processor(connection, ...);
+ *con_cls = pp;
+ return MHD_YES;
+ }
+ if (*upload_data_size)
+ {
+ MHD_post_process(pp, upload_data, *upload_data_size);
+ *upload_data_size = 0;
+ return MHD_YES;
+ }
+ else
+ {
+ MHD_destroy_post_processor(pp);
+ return MHD_queue_response(...);
+ }
+}
+</pre></td></tr></table>
+
+<p>Note that the callback from <code>MHD_OPTION_NOTIFY_COMPLETED</code>
+should be used to destroy the post processor. This cannot be
+done inside of the access handler since the connection may not
+always terminate normally.
+</p>
+
+
+<hr size="6">
+<a name="microhttpd_002dpost-api"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dpost"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo" title="Next
section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost" title="Up
section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Programming-interface-for-the-POST-processor"></a>
+<h2 class="section">9.1 Programming interface for the <code>POST</code>
processor</h2>
+<a name="index-POST-method-4"></a>
+
+<dl>
+<dt><a name="index-MHD_005fcreate_005fpost_005fprocessor"></a><u>Function:</u>
struct MHD_PostProcessor * <b>MHD_create_post_processor</b><i> (struct
MHD_Connection *connection, size_t buffer_size, MHD_PostDataIterator iterator,
void *iterator_cls)</i></dt>
+<dd><p>Create a PostProcessor. A PostProcessor can be used to (incrementally)
+parse the data portion of a <code>POST</code> request.
+</p>
+<dl compact="compact">
+<dt> <var>connection</var></dt>
+<dd><p>the connection on which the <code>POST</code> is happening (used to
determine
+the <code>POST</code> format);
+</p>
+</dd>
+<dt> <var>buffer_size</var></dt>
+<dd><p>maximum number of bytes to use for internal buffering (used only for the
+parsing, specifically the parsing of the keys). A tiny value (256-1024)
+should be sufficient; do <strong>NOT</strong> use a value smaller than 256;
+</p>
+</dd>
+<dt> <var>iterator</var></dt>
+<dd><p>iterator to be called with the parsed data; must <strong>NOT</strong> be
+<code>NULL</code>;
+</p>
+</dd>
+<dt> <var>iterator_cls</var></dt>
+<dd><p>custom value to be used as first argument to <var>iterator</var>.
+</p></dd>
+</dl>
+
+<p>Return <code>NULL</code> on error (out of memory, unsupported encoding),
otherwise
+a PP handle.
+</p></dd></dl>
+
+
+<dl>
+<dt><a name="index-MHD_005fpost_005fprocess"></a><u>Function:</u> int
<b>MHD_post_process</b><i> (struct MHD_PostProcessor *pp, const char
*post_data, size_t post_data_len)</i></dt>
+<dd><p>Parse and process <code>POST</code> data. Call this function when
<code>POST</code>
+data is available (usually during an <code>MHD_AccessHandlerCallback</code>)
+with the <var>upload_data</var> and <var>upload_data_size</var>. Whenever
+possible, this will then cause calls to the
+<code>MHD_IncrementalKeyValueIterator</code>.
+</p>
+<dl compact="compact">
+<dt> <var>pp</var></dt>
+<dd><p>the post processor;
+</p>
+</dd>
+<dt> <var>post_data</var></dt>
+<dd><p><var>post_data_len</var> bytes of <code>POST</code> data;
+</p>
+</dd>
+<dt> <var>post_data_len</var></dt>
+<dd><p>length of <var>post_data</var>.
+</p></dd>
+</dl>
+
+<p>Return <code>MHD_YES</code> on success, <code>MHD_NO</code> on error
+(out-of-memory, iterator aborted, parse error).
+</p></dd></dl>
+
+
+<dl>
+<dt><a
name="index-MHD_005fdestroy_005fpost_005fprocessor"></a><u>Function:</u> int
<b>MHD_destroy_post_processor</b><i> (struct MHD_PostProcessor *pp)</i></dt>
+<dd><p>Release PostProcessor resources. After this function is being called,
+the PostProcessor is guaranteed to no longer call its iterator. There
+is no special call to the iterator to indicate the end of the post processing
+stream. After destroying the PostProcessor, the programmer should
+perform any necessary work to complete the processing of the iterator.
+</p>
+<p>Return <code>MHD_YES</code> if processing completed nicely,
<code>MHD_NO</code>
+if there were spurious characters or formatting problems with
+the post request. It is common to ignore the return value
+of this function.
+</p>
+
+</dd></dl>
+
+
+
+
+<hr size="6">
+<a name="microhttpd_002dinfo"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dpost-api"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo-daemon"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dpost"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#GNU_002dLGPL" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Obtaining-status-information_002e"></a>
+<h1 class="chapter">10. Obtaining status information.</h1>
+
+
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top"><a href="#microhttpd_002dinfo-daemon">10.1
Obtaining state information about an MHD
daemon</a></td><td> </td><td align="left" valign="top"> State
information about an MHD daemon
+</td></tr>
+<tr><td align="left" valign="top"><a href="#microhttpd_002dinfo-conn">10.2
Obtaining state information about a connection</a></td><td> </td><td
align="left" valign="top"> State information about a connection
+</td></tr>
+</table>
+
+
+<hr size="6">
+<a name="microhttpd_002dinfo-daemon"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dinfo"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo-conn"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo" title="Up
section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU_002dLGPL" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Obtaining-state-information-about-an-MHD-daemon"></a>
+<h2 class="section">10.1 Obtaining state information about an MHD daemon</h2>
+
+<dl>
+<dt><a name="index-MHD_005fget_005fdaemon_005finfo"></a><u>Function:</u> const
union MHD_DaemonInfo * <b>MHD_get_daemon_info</b><i> (struct MHD_Daemon
*daemon, enum MHD_DaemonInfoType infoType, ...)</i></dt>
+<dd><p>Obtain information about the given daemon. This function
+is currently not fully implemented.
+</p>
+<dl compact="compact">
+<dt> <var>daemon</var></dt>
+<dd><p>the daemon about which information is desired;
+</p>
+</dd>
+<dt> <var>infoType</var></dt>
+<dd><p>type of information that is desired
+</p>
+</dd>
+<dt> <var>...</var></dt>
+<dd><p>additional arguments about the desired information (depending on
+infoType)
+</p></dd>
+</dl>
+
+<p>Returns a union with the respective member (depending on
+infoType) set to the desired information), or NULL
+in case the desired information is not available or
+applicable.
+</p></dd></dl>
+
+<hr size="6">
+<a name="microhttpd_002dinfo-conn"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dinfo-daemon"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU_002dLGPL" title="Next section
in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo" title="Up
section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU_002dLGPL" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Obtaining-state-information-about-a-connection"></a>
+<h2 class="section">10.2 Obtaining state information about a connection</h2>
+
+
+<dl>
+<dt><a name="index-MHD_005fget_005fconnection_005finfo"></a><u>Function:</u>
const union MHD_ConnectionInfo * <b>MHD_get_connection_info</b><i> (struct
MHD_Connection *daemon, enum MHD_ConnectionInfoType infoType, ...)</i></dt>
+<dd><p>Obtain information about the given connection.
+</p>
+<dl compact="compact">
+<dt> <var>connection</var></dt>
+<dd><p>the connection about which information is desired;
+</p>
+</dd>
+<dt> <var>infoType</var></dt>
+<dd><p>type of information that is desired
+</p>
+</dd>
+<dt> <var>...</var></dt>
+<dd><p>additional arguments about the desired information (depending on
+infoType)
+</p></dd>
+</dl>
+
+<p>Returns a union with the respective member (depending on
+infoType) set to the desired information), or NULL
+in case the desired information is not available or
+applicable.
+</p></dd></dl>
+
+
+
+
+<hr size="6">
+<a name="GNU_002dLGPL"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#microhttpd_002dinfo-conn"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU-GPL-with-eCos-Extension"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#microhttpd_002dinfo"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#GNU-GPL-with-eCos-Extension"
title="Next chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="GNU_002dLGPL-1"></a>
+<h1 class="unnumbered">GNU-LGPL</h1>
+<a name="index-license"></a>
+<p align="center"> Version 2.1, February 1999
+</p>
+
+<table><tr><td> </td><td><pre class="display">Copyright © 1991, 1999
Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+as the successor of the GNU Library Public License, version 2, hence the
+version number 2.1.]
+</pre></td></tr></table>
+
+<a name="Preamble-1"></a>
+<h3 class="subheading">Preamble</h3>
+
+<p> The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software—to make sure the software is free for all its users.
+</p>
+<p> This license, the Lesser General Public License, applies to some
+specially designated software—typically libraries—of the Free
+Software Foundation and other authors who decide to use it. You can use
+it too, but we suggest you first think carefully about whether this
+license or the ordinary General Public License is the better strategy to
+use in any particular case, based on the explanations below.
+</p>
+<p> When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of it
+in new free programs; and that you are informed that you can do these
+things.
+</p>
+<p> To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+</p>
+<p> For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+</p>
+<p> We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+</p>
+<p> To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author’s reputation will not be affected by problems that might be
+introduced by others.
+</p>
+<p> Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+</p>
+<p> Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+</p>
+<p> When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+</p>
+<p> We call this license the <em>Lesser</em> General Public License because it
+does <em>Less</em> to protect the user’s freedom than the ordinary
General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+</p>
+<p> For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+</p>
+<p> In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+</p>
+<p> Although the Lesser General Public License is Less protective of the
+users’ freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+</p>
+<p> The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+“work based on the library” and a “work that uses the
library”. The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+</p>
+<a
name="TERMS-AND-CONDITIONS-FOR-COPYING_002c-DISTRIBUTION-AND-MODIFICATION"></a>
+<h3 class="subheading">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND
MODIFICATION</h3>
+
+<ol>
+<li>
+This License Agreement applies to any software library or other program
+which contains a notice placed by the copyright holder or other
+authorized party saying it may be distributed under the terms of this
+Lesser General Public License (also called “this License”). Each
+licensee is addressed as “you”.
+
+<p> A “library” means a collection of software functions and/or
data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+</p>
+<p> The “Library”, below, refers to any such software library or
work
+which has been distributed under these terms. A “work based on the
+Library” means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term “modification”.)
+</p>
+<p> “Source code” for a work means the preferred form of the work
for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+</p>
+<p> Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+</p>
+</li><li>
+You may copy and distribute verbatim copies of the Library’s
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+<p> You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+</p>
+</li><li>
+You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+<ol>
+<li>
+The modified work must itself be a software library.
+
+</li><li>
+You must cause the files modified to carry prominent notices
+stating that you changed the files and the date of any change.
+
+</li><li>
+You must cause the whole of the work to be licensed at no
+charge to all third parties under the terms of this License.
+
+</li><li>
+If a facility in the modified Library refers to a function or a
+table of data to be supplied by an application program that uses
+the facility, other than as an argument passed when the facility
+is invoked, then you must make a good faith effort to ensure that,
+in the event an application does not supply such function or
+table, the facility still operates, and performs whatever part of
+its purpose remains meaningful.
+
+<p>(For example, a function in a library to compute square roots has
+a purpose that is entirely well-defined independent of the
+application. Therefore, Subsection 2d requires that any
+application-supplied function or table used by this function must
+be optional: if the application does not supply it, the square
+root function must still compute square roots.)
+</p></li></ol>
+
+<p>These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+</p>
+<p>Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+</p>
+<p>In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+</p>
+</li><li>
+You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+<p> Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+</p>
+<p> This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+</p>
+</li><li>
+You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+<p> If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+</p>
+</li><li>
+A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a “work that uses the Library”. Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+<p> However, linking a “work that uses the Library” with the
Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a “work that uses the
+library”. The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+</p>
+<p> When a “work that uses the Library” uses material from a
header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+</p>
+<p> If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+</p>
+<p> Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+</p>
+</li><li>
+As an exception to the Sections above, you may also combine or
+link a “work that uses the Library” with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer’s own use and reverse
+engineering for debugging such modifications.
+
+<p> You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+</p>
+<ol>
+<li>
+Accompany the work with the complete corresponding
+machine-readable source code for the Library including whatever
+changes were used in the work (which must be distributed under
+Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable “work that
+uses the Library”, as object code and/or source code, so that the
+user can modify the Library and then relink to produce a modified
+executable containing the modified Library. (It is understood
+that the user who changes the contents of definitions files in the
+Library will not necessarily be able to recompile the application
+to use the modified definitions.)
+
+</li><li>
+Use a suitable shared library mechanism for linking with the Library. A
+suitable mechanism is one that (1) uses at run time a copy of the
+library already present on the user’s computer system, rather than
+copying library functions into the executable, and (2) will operate
+properly with a modified version of the library, if the user installs
+one, as long as the modified version is interface-compatible with the
+version that the work was made with.
+
+</li><li>
+Accompany the work with a written offer, valid for at
+least three years, to give the same user the materials
+specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+
+</li><li>
+If distribution of the work is made by offering access to copy
+from a designated place, offer equivalent access to copy the above
+specified materials from the same place.
+
+</li><li>
+Verify that the user has already received a copy of these
+materials or that you have already sent this user a copy.
+</li></ol>
+
+<p> For an executable, the required form of the “work that uses the
+Library” must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies the
+executable.
+</p>
+<p> It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+</p>
+</li><li>
+You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+<ol>
+<li>
+Accompany the combined library with a copy of the same work
+based on the Library, uncombined with any other library
+facilities. This must be distributed under the terms of the
+Sections above.
+
+</li><li>
+Give prominent notice with the combined library of the fact
+that part of it is a work based on the Library, and explaining
+where to find the accompanying uncombined form of the same work.
+</li></ol>
+
+</li><li>
+You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+</li><li>
+You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+</li><li>
+Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients’ exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+</li><li>
+If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+<p>If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+</p>
+<p>It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+</p>
+<p>This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+</p>
+</li><li>
+If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+</li><li>
+The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+<p>Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+“any later version”, you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+</p>
+</li><li>
+If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+
+</li><li>
+BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY “AS IS” WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+</li><li>
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+</li></ol>
+
+
+
+<a name="How-to-Apply-These-Terms-to-Your-New-Libraries"></a>
+<h3 class="subheading">How to Apply These Terms to Your New Libraries</h3>
+
+<p> If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+</p>
+<p> To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+“copyright” line and a pointer to where the full notice is found.
+</p>
+<table><tr><td> </td><td><pre class="smallexample"><var>one line to give
the library's name and an idea of what it does.</var>
+Copyright (C) <var>year</var> <var>name of author</var>
+
+This library is free software; you can redistribute it and/or modify it
+under the terms of the GNU Lesser General Public License as published by
+the Free Software Foundation; either version 2.1 of the License, or (at
+your option) any later version.
+
+This library is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with this library; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
+USA.
+</pre></td></tr></table>
+
+<p>Also add information on how to contact you by electronic and paper mail.
+</p>
+<p>You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a “copyright disclaimer” for the library,
if
+necessary. Here is a sample; alter the names:
+</p>
+<table><tr><td> </td><td><pre class="smallexample">Yoyodyne, Inc., hereby
disclaims all copyright interest in the library
+`Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+<var>signature of Ty Coon</var>, 1 April 1990
+Ty Coon, President of Vice
+</pre></td></tr></table>
+
+<p>That’s all there is to it!
+</p>
+<hr size="6">
+<a name="GNU-GPL-with-eCos-Extension"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#GNU_002dLGPL" title="Previous
section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a
href="#How-to-Apply-These-Terms-to-Your-New-Programs" title="Next section in
reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#GNU_002dLGPL" title="Beginning of
this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#GNU_002dFDL" title="Next chapter">
>> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="GNU-GPL-with-eCos-Extension-1"></a>
+<h1 class="unnumbered">GNU GPL with eCos Extension</h1>
+<a name="index-license-1"></a>
+<a name="index-GPL_002c-GNU-General-Public-License"></a>
+<a name="index-eCos_002c-GNU-General-Public-License-with-eCos-Extension"></a>
+<p align="center"> Version 2, June 1991
+</p>
+<table><tr><td> </td><td><pre class="display">Copyright © 1989, 1991
Free Software Foundation, Inc.
+59 Temple Place – Suite 330, Boston, MA 02111-1307, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></td></tr></table>
+
+
+
+
+<a name="Preamble"></a>
+<h3 class="subheading">Preamble</h3>
+
+<p> The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software—to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation’s software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+</p>
+<p> When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+</p>
+<p> To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+</p>
+<p> For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+</p>
+<p> We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+</p>
+<p> Also, for each author’s protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors’ reputations.
+</p>
+<p> Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone’s free use or not licensed at all.
+</p>
+<p> The precise terms and conditions for copying, distribution and
+modification follow.
+</p>
+
+<ol>
+<li>
+This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The “Program”,
below,
+refers to any such program or work, and a “work based on the
Program”
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term “modification”.) Each licensee is addressed as
“you”.
+
+<p>Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+</p>
+</li><li>
+You may copy and distribute verbatim copies of the Program’s
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+<p>You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+</p>
+</li><li>
+You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+<ol>
+<li>
+You must cause the modified files to carry prominent notices
+stating that you changed the files and the date of any change.
+
+</li><li>
+You must cause any work that you distribute or publish, that in
+whole or in part contains or is derived from the Program or any
+part thereof, to be licensed as a whole at no charge to all third
+parties under the terms of this License.
+
+</li><li>
+If the modified program normally reads commands interactively
+when run, you must cause it, when started running for such
+interactive use in the most ordinary way, to print or display an
+announcement including an appropriate copyright notice and a
+notice that there is no warranty (or else, saying that you provide
+a warranty) and that users may redistribute the program under
+these conditions, and telling the user how to view a copy of this
+License. (Exception: if the Program itself is interactive but
+does not normally print such an announcement, your work based on
+the Program is not required to print an announcement.)
+</li></ol>
+
+<p>These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+</p>
+<p>Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+</p>
+<p>In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+</p>
+</li><li>
+You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+<ol>
+<li>
+Accompany it with the complete corresponding machine-readable
+source code, which must be distributed under the terms of Sections
+1 and 2 above on a medium customarily used for software interchange; or,
+
+</li><li>
+Accompany it with a written offer, valid for at least three
+years, to give any third party, for a charge no more than your
+cost of physically performing source distribution, a complete
+machine-readable copy of the corresponding source code, to be
+distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange; or,
+
+</li><li>
+Accompany it with the information you received as to the offer
+to distribute corresponding source code. (This alternative is
+allowed only for noncommercial distribution and only if you
+received the program in object code or executable form with such
+an offer, in accord with Subsection b above.)
+</li></ol>
+
+<p>The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+</p>
+<p>If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+</p>
+</li><li>
+You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+</li><li>
+You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+</li><li>
+Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients’ exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+</li><li>
+If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+<p>If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+</p>
+<p>It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+</p>
+<p>This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+</p>
+</li><li>
+If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+</li><li>
+The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+<p>Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and “any
+later version”, you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+</p>
+</li><li>
+If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+
+</li><li>
+BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+</li><li>
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+
+
+</li><li>
+As a special exception, if other files instantiate templates or use
+macros or inline functions from this file, or you compile this file
+and link it with other works to produce a work based on this file,
+this file does not by itself cause the resulting work to be covered by
+the GNU General Public License. However the source code for this file
+must still be made available in accordance with section (3) of the GNU
+General Public License v2.
+
+<p>This exception does not invalidate any other reasons why a work based
+on this file might be covered by the GNU General Public License.
+</p>
+</li></ol>
+
+
+
+
+<hr size="6">
+<a name="How-to-Apply-These-Terms-to-Your-New-Programs"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#GNU-GPL-with-eCos-Extension"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU_002dFDL" title="Next section
in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#GNU-GPL-with-eCos-Extension"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU-GPL-with-eCos-Extension"
title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU_002dFDL" title="Next chapter">
>> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<h2 class="unnumberedsec">How to Apply These Terms to Your New Programs</h2>
+
+<p> If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+</p>
+<p> To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the “copyright” line and a pointer to where the full notice is
found.
+</p>
+<table><tr><td> </td><td><pre class="smallexample"><var>one line to give
the program's name and an idea of what it does.</var>
+Copyright (C) 19<var>yy</var> <var>name of author</var>
+
+This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License
+as published by the Free Software Foundation; either version 2
+of the License, or (at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License along
+with this program; if not, write to the Free Software Foundation, Inc.,
+59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
+</pre></td></tr></table>
+
+<p>Also add information on how to contact you by electronic and paper mail.
+</p>
+<p>If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+</p>
+<table><tr><td> </td><td><pre class="smallexample">Gnomovision version
69, Copyright (C) 19<var>yy</var> <var>name of author</var>
+Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
+type `show w'. This is free software, and you are welcome
+to redistribute it under certain conditions; type `show c'
+for details.
+</pre></td></tr></table>
+
+<p>The hypothetical commands ‘<samp>show w</samp>’ and
‘<samp>show c</samp>’ should show
+the appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than ‘<samp>show
w</samp>’ and
+‘<samp>show c</samp>’; they could even be mouse-clicks or menu
items—whatever
+suits your program.
+</p>
+<p>You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a “copyright disclaimer” for the program,
if
+necessary. Here is a sample; alter the names:
+</p>
+<table><tr><td> </td><td><pre class="smallexample">Yoyodyne, Inc., hereby
disclaims all copyright
+interest in the program `Gnomovision'
+(which makes passes at compilers) written
+by James Hacker.
+
+<var>signature of Ty Coon</var>, 1 April 1989
+Ty Coon, President of Vice
+</pre></td></tr></table>
+
+<p>This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
+</p>
+<hr size="6">
+<a name="GNU_002dFDL"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a
href="#How-to-Apply-These-Terms-to-Your-New-Programs" title="Previous section
in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index" title="Next section
in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#GNU-GPL-with-eCos-Extension"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index" title="Next
chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="GNU_002dFDL-1"></a>
+<h1 class="unnumbered">GNU-FDL</h1>
+<a name="index-license-2"></a>
+<p align="center"> Version 1.3, 3 November 2008
+</p>
+
+<table><tr><td> </td><td><pre class="display">Copyright © 2000,
2001, 2002, 2007, 2008 Free Software Foundation, Inc.
+<a href="http://fsf.org/";>http://fsf.org/</a>
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></td></tr></table>
+
+<ol>
+<li>
+PREAMBLE
+
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+</p>
+<p>This License is a kind of “copyleft”, which means that
derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+</p>
+<p>We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+</p>
+</li><li>
+APPLICABILITY AND DEFINITIONS
+
+<p>This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein. The “Document”, below,
+refers to any such manual or work. Any member of the public is a
+licensee, and is addressed as “you”. You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+</p>
+<p>A “Modified Version” of the Document means any work containing
the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+</p>
+<p>A “Secondary Section” is a named appendix or a front-matter
section
+of the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document’s overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject. (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.) The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+</p>
+<p>The “Invariant Sections” are certain Secondary Sections whose
titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License. If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant. The Document may contain zero
+Invariant Sections. If the Document does not identify any Invariant
+Sections then there are none.
+</p>
+<p>The “Cover Texts” are certain short passages of text that are
listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License. A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+</p>
+<p>A “Transparent” copy of the Document means a machine-readable
copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters. A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text. A copy that is not “Transparent” is called
“Opaque”.
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
+<small>ASCII</small> without markup, Texinfo input format, LaTeX input
+format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly
available
+<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
+PostScript or <acronym>PDF</acronym> designed for human modification. Examples
+of transparent image formats include <acronym>PNG</acronym>,
<acronym>XCF</acronym> and
+<acronym>JPG</acronym>. Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, <acronym>SGML</acronym> or
+<acronym>XML</acronym> for which the <acronym>DTD</acronym> and/or processing
tools are
+not generally available, and the machine-generated <acronym>HTML</acronym>,
+PostScript or <acronym>PDF</acronym> produced by some word processors for
+output purposes only.
+</p>
+<p>The “Title Page” means, for a printed book, the title page
itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in
+formats which do not have any title page as such, “Title Page”
means
+the text near the most prominent appearance of the work’s title,
+preceding the beginning of the body of the text.
+</p>
+<p>The “publisher” means any person or entity that distributes
copies
+of the Document to the public.
+</p>
+<p>A section “Entitled XYZ” means a named subunit of the Document
whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language. (Here XYZ stands for a
+specific section name mentioned below, such as “Acknowledgements”,
+“Dedications”, “Endorsements”, or
“History”.) To “Preserve the Title”
+of such a section when you modify the Document means that it remains a
+section “Entitled XYZ” according to this definition.
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document. These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+</p>
+</li><li>
+VERBATIM COPYING
+
+<p>You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+</p>
+</li><li>
+COPYING IN QUANTITY
+
+<p>If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document’s license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover. Both covers must also clearly and legibly identify
+you as the publisher of these copies. The front cover must present
+the full title with all words of the title equally prominent and
+visible. You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+</p>
+<p>If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+</p>
+<p>It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+</p>
+</li><li>
+MODIFICATIONS
+
+<p>You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:
+</p>
+<ol>
+<li>
+Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions
+(which should, if there were any, be listed in the History section
+of the Document). You may use the same title as a previous version
+if the original publisher of that version gives permission.
+
+</li><li>
+List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
+
+</li><li>
+State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
+</li><li>
+Preserve all the copyright notices of the Document.
+
+</li><li>
+Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
+</li><li>
+Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.
+
+</li><li>
+Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document’s license notice.
+
+</li><li>
+Include an unaltered copy of this License.
+
+</li><li>
+Preserve the section Entitled “History”, Preserve its Title, and
add
+to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page. If
+there is no section Entitled “History” in the Document, create one
+stating the title, year, authors, and publisher of the Document as
+given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.
+
+</li><li>
+Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise
+the network locations given in the Document for previous versions
+it was based on. These may be placed in the “History” section.
+You may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.
+
+</li><li>
+For any section Entitled “Acknowledgements” or
“Dedications”, Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
+
+</li><li>
+Preserve all the Invariant Sections of the Document,
+unaltered in their text and in their titles. Section numbers
+or the equivalent are not considered part of the section titles.
+
+</li><li>
+Delete any section Entitled “Endorsements”. Such a section
+may not be included in the Modified Version.
+
+</li><li>
+Do not retitle any existing section to be Entitled “Endorsements”
or
+to conflict in title with any Invariant Section.
+
+</li><li>
+Preserve any Warranty Disclaimers.
+</li></ol>
+
+<p>If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant. To do this, add their titles to the
+list of Invariant Sections in the Modified Version’s license notice.
+These titles must be distinct from any other section titles.
+</p>
+<p>You may add a section Entitled “Endorsements”, provided it
contains
+nothing but endorsements of your Modified Version by various
+parties—for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+</p>
+</li><li>
+COMBINING DOCUMENTS
+
+<p>You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+</p>
+<p>The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+</p>
+<p>In the combination, you must combine any sections Entitled
“History”
+in the various original documents, forming one section Entitled
+“History”; likewise combine any sections Entitled
“Acknowledgements”,
+and any sections Entitled “Dedications”. You must delete all
+sections Entitled “Endorsements.”
+</p>
+</li><li>
+COLLECTIONS OF DOCUMENTS
+
+<p>You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+</p>
+<p>You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+</p>
+</li><li>
+AGGREGATION WITH INDEPENDENT WORKS
+
+<p>A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an “aggregate” if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation’s users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document’s Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+</p>
+</li><li>
+TRANSLATION
+
+<p>Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers. In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+</p>
+<p>If a section in the Document is Entitled “Acknowledgements”,
+“Dedications”, or “History”, the requirement (section
4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+</p>
+</li><li>
+TERMINATION
+
+<p>You may not copy, modify, sublicense, or distribute the Document
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense, or distribute it is void, and
+will automatically terminate your rights under this License.
+</p>
+<p>However, if you cease all violation of this License, then your license
+from a particular copyright holder is reinstated (a) provisionally,
+unless and until the copyright holder explicitly and finally
+terminates your license, and (b) permanently, if the copyright holder
+fails to notify you of the violation by some reasonable means prior to
+60 days after the cessation.
+</p>
+<p>Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+</p>
+<p>Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, receipt of a copy of some or all of the same material does
+not give you any rights to use it.
+</p>
+</li><li>
+FUTURE REVISIONS OF THIS LICENSE
+
+<p>The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns. See
+<a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
+</p>
+<p>Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License “or any later version” applies to it, you have the option
of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation. If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation. If the Document
+specifies that a proxy can decide which future versions of this
+License can be used, that proxy’s public statement of acceptance of a
+version permanently authorizes you to choose that version for the
+Document.
+</p>
+</li><li>
+RELICENSING
+
+<p>“Massive Multiauthor Collaboration Site” (or “MMC
Site”) means any
+World Wide Web server that publishes copyrightable works and also
+provides prominent facilities for anybody to edit those works. A
+public wiki that anybody can edit is an example of such a server. A
+“Massive Multiauthor Collaboration” (or “MMC”)
contained in the
+site means any set of copyrightable works thus published on the MMC
+site.
+</p>
+<p>“CC-BY-SA” means the Creative Commons Attribution-Share Alike
3.0
+license published by Creative Commons Corporation, a not-for-profit
+corporation with a principal place of business in San Francisco,
+California, as well as future copyleft versions of that license
+published by that same organization.
+</p>
+<p>“Incorporate” means to publish or republish a Document, in
whole or
+in part, as part of another Document.
+</p>
+<p>An MMC is “eligible for relicensing” if it is licensed under
this
+License, and if all works that were first published under this License
+somewhere other than this MMC, and subsequently incorporated in whole
+or in part into the MMC, (1) had no cover texts or invariant sections,
+and (2) were thus incorporated prior to November 1, 2008.
+</p>
+<p>The operator of an MMC Site may republish an MMC contained in the site
+under CC-BY-SA on the same site at any time before August 1, 2009,
+provided the MMC is eligible for relicensing.
+</p>
+</li></ol>
+
+
+<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
+<h2 class="heading">ADDENDUM: How to use this License for your documents</h2>
+
+<p>To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+</p>
+<table><tr><td> </td><td><pre class="smallexample"> Copyright (C)
<var>year</var> <var>your name</var>.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.3
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+ Texts. A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
+</pre></td></tr></table>
+
+<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the “with…Texts.” line with this:
+</p>
+<table><tr><td> </td><td><pre class="smallexample"> with the Invariant
Sections being <var>list their titles</var>, with
+ the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts
+ being <var>list</var>.
+</pre></td></tr></table>
+
+<p>If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+</p>
+<p>If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
+</p>
+
+
+<hr size="6">
+<a name="Concept-Index"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#GNU_002dFDL" title="Previous
section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#Function-and-Data-Index"
title="Next section in reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#GNU_002dFDL" title="Beginning of
this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#Function-and-Data-Index"
title="Next chapter"> >> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Concept-Index-1"></a>
+<h1 class="unnumbered">Concept Index</h1>
+
+<table><tr><th valign="top">Jump to: </th><td><a
href="#Concept-Index-1_cp_letter-B" class="summary-letter"><b>B</b></a>
+
+<a href="#Concept-Index-1_cp_letter-C" class="summary-letter"><b>C</b></a>
+
+<a href="#Concept-Index-1_cp_letter-D" class="summary-letter"><b>D</b></a>
+
+<a href="#Concept-Index-1_cp_letter-E" class="summary-letter"><b>E</b></a>
+
+<a href="#Concept-Index-1_cp_letter-F" class="summary-letter"><b>F</b></a>
+
+<a href="#Concept-Index-1_cp_letter-G" class="summary-letter"><b>G</b></a>
+
+<a href="#Concept-Index-1_cp_letter-I" class="summary-letter"><b>I</b></a>
+
+<a href="#Concept-Index-1_cp_letter-L" class="summary-letter"><b>L</b></a>
+
+<a href="#Concept-Index-1_cp_letter-M" class="summary-letter"><b>M</b></a>
+
+<a href="#Concept-Index-1_cp_letter-O" class="summary-letter"><b>O</b></a>
+
+<a href="#Concept-Index-1_cp_letter-P" class="summary-letter"><b>P</b></a>
+
+<a href="#Concept-Index-1_cp_letter-Q" class="summary-letter"><b>Q</b></a>
+
+<a href="#Concept-Index-1_cp_letter-S" class="summary-letter"><b>S</b></a>
+
+<a href="#Concept-Index-1_cp_letter-T" class="summary-letter"><b>T</b></a>
+
+</td></tr></table>
+<table border="0" class="index-cp">
+<tr><td></td><th align="left">Index Entry</th><th align="left">
Section</th></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-B">B</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-bind_002c-restricting-bind">bind, restricting bind</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-C">C</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-connection_002c-limiting-number-of-connections">connection,
limiting number of connections</a></td><td valign="top"><a
href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-cookie">cookie</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-D">D</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-debugging">debugging</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-debugging-1">debugging</a></td><td valign="top"><a
href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-eCos_002c-GNU-General-Public-License-with-eCos-Extension">eCos,
GNU General Public License with eCos Extension</a></td><td valign="top"><a
href="#GNU-GPL-with-eCos-Extension">GNU GPL with eCos Extension</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-F">F</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-FD_005fSETSIZE">FD_SETSIZE</a></td><td valign="top"><a
href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-G">G</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-GPL_002c-GNU-General-Public-License">GPL, GNU General Public
License</a></td><td valign="top"><a href="#GNU-GPL-with-eCos-Extension">GNU GPL
with eCos Extension</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-I">I</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-IPv6">IPv6</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-L">L</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-license">license</a></td><td
valign="top"><a href="#GNU_002dLGPL">GNU-LGPL</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-license-1">license</a></td><td
valign="top"><a href="#GNU-GPL-with-eCos-Extension">GNU GPL with eCos
Extension</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-license-2">license</a></td><td
valign="top"><a href="#GNU_002dFDL">GNU-FDL</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-listen">listen</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-logging">logging</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-logging-1">logging</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-memory_002c-limiting-memory-utilization">memory, limiting memory
utilization</a></td><td valign="top"><a href="#microhttpd_002dconst">2.
Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-O">O</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-options">options</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-P">P</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-poll">poll</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-POST-method">POST
method</a></td><td valign="top"><a href="#microhttpd_002dconst">2.
Constants</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-POST-method-1">POST
method</a></td><td valign="top"><a href="#microhttpd_002dstruct">3. Structures
type definition</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-POST-method-2">POST
method</a></td><td valign="top"><a href="#microhttpd_002dcb">4. Callback
functions definition</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-POST-method-3">POST
method</a></td><td valign="top"><a href="#microhttpd_002dpost">9. Adding a
<code>POST</code> processor</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-POST-method-4">POST
method</a></td><td valign="top"><a href="#microhttpd_002dpost-api">9.1
Programming interface for the <code>POST</code> processor</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-PUT-method">PUT
method</a></td><td valign="top"><a href="#microhttpd_002dcb">4. Callback
functions definition</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-Q">Q</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-query-string">query
string</a></td><td valign="top"><a href="#microhttpd_002dconst">2.
Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-S">S</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-select">select</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Concept-Index-1_cp_letter-T">T</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-timeout">timeout</a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-timeout-1">timeout</a></td><td
valign="top"><a href="#microhttpd_002dinspect">6. Implementing external
<code>select</code></a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-timeout-2">timeout</a></td><td
valign="top"><a href="#microhttpd_002dinspect">6. Implementing external
<code>select</code></a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: </th><td><a
href="#Concept-Index-1_cp_letter-B" class="summary-letter"><b>B</b></a>
+
+<a href="#Concept-Index-1_cp_letter-C" class="summary-letter"><b>C</b></a>
+
+<a href="#Concept-Index-1_cp_letter-D" class="summary-letter"><b>D</b></a>
+
+<a href="#Concept-Index-1_cp_letter-E" class="summary-letter"><b>E</b></a>
+
+<a href="#Concept-Index-1_cp_letter-F" class="summary-letter"><b>F</b></a>
+
+<a href="#Concept-Index-1_cp_letter-G" class="summary-letter"><b>G</b></a>
+
+<a href="#Concept-Index-1_cp_letter-I" class="summary-letter"><b>I</b></a>
+
+<a href="#Concept-Index-1_cp_letter-L" class="summary-letter"><b>L</b></a>
+
+<a href="#Concept-Index-1_cp_letter-M" class="summary-letter"><b>M</b></a>
+
+<a href="#Concept-Index-1_cp_letter-O" class="summary-letter"><b>O</b></a>
+
+<a href="#Concept-Index-1_cp_letter-P" class="summary-letter"><b>P</b></a>
+
+<a href="#Concept-Index-1_cp_letter-Q" class="summary-letter"><b>Q</b></a>
+
+<a href="#Concept-Index-1_cp_letter-S" class="summary-letter"><b>S</b></a>
+
+<a href="#Concept-Index-1_cp_letter-T" class="summary-letter"><b>T</b></a>
+
+</td></tr></table>
+
+<hr size="6">
+<a name="Function-and-Data-Index"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Concept-Index" title="Previous
section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[<a href="#Type-Index" title="Next section in
reading order"> > </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Concept-Index" title="Beginning of
this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[<a href="#Type-Index" title="Next chapter">
>> </a>]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Function-and-Data-Index-1"></a>
+<h1 class="unnumbered">Function and Data Index</h1>
+
+<table><tr><th valign="top">Jump to: </th><td><a
href="#Function-and-Data-Index-1_fn_symbol-1"
class="summary-letter"><b>*</b></a>
+
+<br>
+<a href="#Function-and-Data-Index-1_fn_letter-M"
class="summary-letter"><b>M</b></a>
+
+</td></tr></table>
+<table border="0" class="index-fn">
+<tr><td></td><th align="left">Index Entry</th><th align="left">
Section</th></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a
name="Function-and-Data-Index-1_fn_symbol-1">*</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-_002aMHD_005fAcceptPolicyCallback"><code>*MHD_AcceptPolicyCallback</code></a></td><td
valign="top"><a href="#microhttpd_002dcb">4. Callback functions
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-_002aMHD_005fAccessHandlerCallback"><code>*MHD_AccessHandlerCallback</code></a></td><td
valign="top"><a href="#microhttpd_002dcb">4. Callback functions
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-_002aMHD_005fContentReaderCallback"><code>*MHD_ContentReaderCallback</code></a></td><td
valign="top"><a href="#microhttpd_002dcb">4. Callback functions
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-_002aMHD_005fContentReaderFreeCallback"><code>*MHD_ContentReaderFreeCallback</code></a></td><td
valign="top"><a href="#microhttpd_002dcb">4. Callback functions
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-_002aMHD_005fKeyValueIterator"><code>*MHD_KeyValueIterator</code></a></td><td
valign="top"><a href="#microhttpd_002dcb">4. Callback functions
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-_002aMHD_005fPostDataIterator"><code>*MHD_PostDataIterator</code></a></td><td
valign="top"><a href="#microhttpd_002dcb">4. Callback functions
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-_002aMHD_005fRequestCompletedCallback"><code>*MHD_RequestCompletedCallback</code></a></td><td
valign="top"><a href="#microhttpd_002dcb">4. Callback functions
definition</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a
name="Function-and-Data-Index-1_fn_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fadd_005fresponse_005fheader"><code>MHD_add_response_header</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-headers">8.3 Adding headers to
a response</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fcreate_005fpost_005fprocessor"><code>MHD_create_post_processor</code></a></td><td
valign="top"><a href="#microhttpd_002dpost-api">9.1 Programming interface for
the <code>POST</code> processor</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fcreate_005fresponse_005ffrom_005fcallback"><code>MHD_create_response_from_callback</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-create">8.2 Creating response
objects</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fcreate_005fresponse_005ffrom_005fdata"><code>MHD_create_response_from_data</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-create">8.2 Creating response
objects</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fdel_005fresponse_005fheader"><code>MHD_del_response_header</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-headers">8.3 Adding headers to
a response</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fdestroy_005fpost_005fprocessor"><code>MHD_destroy_post_processor</code></a></td><td
valign="top"><a href="#microhttpd_002dpost-api">9.1 Programming interface for
the <code>POST</code> processor</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fdestroy_005fresponse"><code>MHD_destroy_response</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-enqueue">8.1 Enqueuing a
response</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fget_005fconnection_005finfo"><code>MHD_get_connection_info</code></a></td><td
valign="top"><a href="#microhttpd_002dinfo-conn">10.2 Obtaining state
information about a connection</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fget_005fconnection_005fvalues"><code>MHD_get_connection_values</code></a></td><td
valign="top"><a href="#microhttpd_002drequests">7. Handling
requests</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fget_005fdaemon_005finfo"><code>MHD_get_daemon_info</code></a></td><td
valign="top"><a href="#microhttpd_002dinfo-daemon">10.1 Obtaining state
information about an MHD daemon</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fget_005ffdset"><code>MHD_get_fdset</code></a></td><td
valign="top"><a href="#microhttpd_002dinspect">6. Implementing external
<code>select</code></a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fget_005fresponse_005fheader"><code>MHD_get_response_header</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-inspect">8.4 Inspecting a
response object</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fget_005fresponse_005fheaders"><code>MHD_get_response_headers</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-inspect">8.4 Inspecting a
response object</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fget_005ftimeout"><code>MHD_get_timeout</code></a></td><td
valign="top"><a href="#microhttpd_002dinspect">6. Implementing external
<code>select</code></a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005flookup_005fconnection_005fvalue"><code>MHD_lookup_connection_value</code></a></td><td
valign="top"><a href="#microhttpd_002drequests">7. Handling
requests</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fpost_005fprocess"><code>MHD_post_process</code></a></td><td
valign="top"><a href="#microhttpd_002dpost-api">9.1 Programming interface for
the <code>POST</code> processor</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fqueue_005fresponse"><code>MHD_queue_response</code></a></td><td
valign="top"><a href="#microhttpd_002dresponse-enqueue">8.1 Enqueuing a
response</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005frun"><code>MHD_run</code></a></td><td valign="top"><a
href="#microhttpd_002dinit">5. Starting and stopping the server</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fset_005fconnection_005fvalue"><code>MHD_set_connection_value</code></a></td><td
valign="top"><a href="#microhttpd_002drequests">7. Handling
requests</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fset_005fpanic_005ffunc"><code>MHD_set_panic_func</code></a></td><td
valign="top"><a href="#microhttpd_002dinit">5. Starting and stopping the
server</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fstart_005fdaemon"><code>MHD_start_daemon</code></a></td><td
valign="top"><a href="#microhttpd_002dinit">5. Starting and stopping the
server</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fstop_005fdaemon"><code>MHD_stop_daemon</code></a></td><td
valign="top"><a href="#microhttpd_002dinit">5. Starting and stopping the
server</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: </th><td><a
href="#Function-and-Data-Index-1_fn_symbol-1"
class="summary-letter"><b>*</b></a>
+
+<br>
+<a href="#Function-and-Data-Index-1_fn_letter-M"
class="summary-letter"><b>M</b></a>
+
+</td></tr></table>
+
+<hr size="6">
+<a name="Type-Index"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Function-and-Data-Index"
title="Previous section in reading order"> < </a>]</td>
+<td valign="middle" align="left">[ > ]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Function-and-Data-Index"
title="Beginning of this chapter or previous chapter"> << </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up
</a>]</td>
+<td valign="middle" align="left">[ >> ]</td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left"> </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<a name="Type-Index-1"></a>
+<h1 class="unnumbered">Type Index</h1>
+
+<table><tr><th valign="top">Jump to: </th><td><a
href="#Type-Index-1_tp_letter-M" class="summary-letter"><b>M</b></a>
+
+</td></tr></table>
+<table border="0" class="index-tp">
+<tr><td></td><th align="left">Index Entry</th><th align="left">
Section</th></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Type-Index-1_tp_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fConnection"><code>MHD_Connection</code></a></td><td
valign="top"><a href="#microhttpd_002dstruct">3. Structures type
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fConnectionInfo"><code>MHD_ConnectionInfo</code></a></td><td
valign="top"><a href="#microhttpd_002dstruct">3. Structures type
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fConnectionInfoType"><code>MHD_ConnectionInfoType</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fDaemon"><code>MHD_Daemon</code></a></td><td
valign="top"><a href="#microhttpd_002dstruct">3. Structures type
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fDaemonInfo"><code>MHD_DaemonInfo</code></a></td><td
valign="top"><a href="#microhttpd_002dstruct">3. Structures type
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fDaemonInfoType"><code>MHD_DaemonInfoType</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fFLAG"><code>MHD_FLAG</code></a></td><td valign="top"><a
href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fGNUTLS_005fCipherAlgorithm"><code>MHD_GNUTLS_CipherAlgorithm</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fGNUTLS_005fProtocol"><code>MHD_GNUTLS_Protocol</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fOPTION"><code>MHD_OPTION</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fOptionItem"><code>MHD_OptionItem</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fPostProcessor"><code>MHD_PostProcessor</code></a></td><td
valign="top"><a href="#microhttpd_002dstruct">3. Structures type
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fRequestTerminationCode"><code>MHD_RequestTerminationCode</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fResponse"><code>MHD_Response</code></a></td><td
valign="top"><a href="#microhttpd_002dstruct">3. Structures type
definition</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-MHD_005fValueKind"><code>MHD_ValueKind</code></a></td><td
valign="top"><a href="#microhttpd_002dconst">2. Constants</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: </th><td><a
href="#Type-Index-1_tp_letter-M" class="summary-letter"><b>M</b></a>
+
+</td></tr></table>
+
+<hr size="6">
+<a name="SEC_Foot"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<h1>Footnotes</h1>
+<h3><a name="FOOT1" href="#DOCF1">(1)</a></h3>
+<p>Note to readers acquainted
+to the Tcl <acronym>API</acronym>: reference counting on
<code>MHD_Connection</code>
+structures is handled in the same way as Tcl handles <code>Tcl_Obj</code>
+structures through <code>Tcl_IncrRefCount()</code> and
+<code>Tcl_DecrRefCount()</code>.
+</p><hr size="1">
+<a name="SEC_Contents"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<h1>Table of Contents</h1>
+<div class="contents">
+
+<ul class="toc">
+ <li><a name="toc-Introduction" href="#microhttpd_002dintro">1.
Introduction</a></li>
+ <li><a name="toc-Constants" href="#microhttpd_002dconst">2.
Constants</a></li>
+ <li><a name="toc-Structures-type-definition"
href="#microhttpd_002dstruct">3. Structures type definition</a></li>
+ <li><a name="toc-Callback-functions-definition" href="#microhttpd_002dcb">4.
Callback functions definition</a></li>
+ <li><a name="toc-Starting-and-stopping-the-server"
href="#microhttpd_002dinit">5. Starting and stopping the server</a></li>
+ <li><a name="toc-Implementing-external-select"
href="#microhttpd_002dinspect">6. Implementing external
<code>select</code></a></li>
+ <li><a name="toc-Handling-requests" href="#microhttpd_002drequests">7.
Handling requests</a></li>
+ <li><a name="toc-Building-answers-to-responses"
href="#microhttpd_002dresponses">8. Building answers to responses</a>
+ <ul class="toc">
+ <li><a name="toc-Enqueuing-a-response"
href="#microhttpd_002dresponse-enqueue">8.1 Enqueuing a response</a></li>
+ <li><a name="toc-Creating-response-objects"
href="#microhttpd_002dresponse-create">8.2 Creating response objects</a></li>
+ <li><a name="toc-Adding-headers-to-a-response"
href="#microhttpd_002dresponse-headers">8.3 Adding headers to a
response</a></li>
+ <li><a name="toc-Inspecting-a-response-object"
href="#microhttpd_002dresponse-inspect">8.4 Inspecting a response
object</a></li>
+ </ul></li>
+ <li><a name="toc-Adding-a-POST-processor" href="#microhttpd_002dpost">9.
Adding a <code>POST</code> processor</a>
+ <ul class="toc">
+ <li><a name="toc-Programming-interface-for-the-POST-processor"
href="#microhttpd_002dpost-api">9.1 Programming interface for the
<code>POST</code> processor</a></li>
+ </ul></li>
+ <li><a name="toc-Obtaining-status-information_002e"
href="#microhttpd_002dinfo">10. Obtaining status information.</a>
+ <ul class="toc">
+ <li><a name="toc-Obtaining-state-information-about-an-MHD-daemon"
href="#microhttpd_002dinfo-daemon">10.1 Obtaining state information about an
MHD daemon</a></li>
+ <li><a name="toc-Obtaining-state-information-about-a-connection"
href="#microhttpd_002dinfo-conn">10.2 Obtaining state information about a
connection</a></li>
+ </ul></li>
+ <li><a name="toc-GNU_002dLGPL-1" href="#GNU_002dLGPL">GNU-LGPL</a></li>
+ <li><a name="toc-GNU-GPL-with-eCos-Extension-1"
href="#GNU-GPL-with-eCos-Extension">GNU GPL with eCos Extension</a>
+ <ul class="toc">
+ <li><a name="toc-How-to-Apply-These-Terms-to-Your-New-Programs"
href="#How-to-Apply-These-Terms-to-Your-New-Programs">How to Apply These Terms
to Your New Programs</a></li>
+ </ul></li>
+ <li><a name="toc-GNU_002dFDL-1" href="#GNU_002dFDL">GNU-FDL</a></li>
+ <li><a name="toc-Concept-Index-1" href="#Concept-Index">Concept
Index</a></li>
+ <li><a name="toc-Function-and-Data-Index-1"
href="#Function-and-Data-Index">Function and Data Index</a></li>
+ <li><a name="toc-Type-Index-1" href="#Type-Index">Type Index</a></li>
+</ul>
+</div>
+<hr size="1">
+<a name="SEC_Overview"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<h1>Short Table of Contents</h1>
+<div class="shortcontents">
+<ul class="toc">
+<li><a name="stoc-Introduction" href="#microhttpd_002dintro">1.
Introduction</a></li>
+<li><a name="stoc-Constants" href="#microhttpd_002dconst">2. Constants</a></li>
+<li><a name="stoc-Structures-type-definition" href="#microhttpd_002dstruct">3.
Structures type definition</a></li>
+<li><a name="stoc-Callback-functions-definition" href="#microhttpd_002dcb">4.
Callback functions definition</a></li>
+<li><a name="stoc-Starting-and-stopping-the-server"
href="#microhttpd_002dinit">5. Starting and stopping the server</a></li>
+<li><a name="stoc-Implementing-external-select"
href="#microhttpd_002dinspect">6. Implementing external
<code>select</code></a></li>
+<li><a name="stoc-Handling-requests" href="#microhttpd_002drequests">7.
Handling requests</a></li>
+<li><a name="stoc-Building-answers-to-responses"
href="#microhttpd_002dresponses">8. Building answers to responses</a></li>
+<li><a name="stoc-Adding-a-POST-processor" href="#microhttpd_002dpost">9.
Adding a <code>POST</code> processor</a></li>
+<li><a name="stoc-Obtaining-status-information_002e"
href="#microhttpd_002dinfo">10. Obtaining status information.</a></li>
+<li><a name="stoc-GNU_002dLGPL-1" href="#GNU_002dLGPL">GNU-LGPL</a></li>
+<li><a name="stoc-GNU-GPL-with-eCos-Extension-1"
href="#GNU-GPL-with-eCos-Extension">GNU GPL with eCos Extension</a></li>
+<li><a name="stoc-GNU_002dFDL-1" href="#GNU_002dFDL">GNU-FDL</a></li>
+<li><a name="stoc-Concept-Index-1" href="#Concept-Index">Concept Index</a></li>
+<li><a name="stoc-Function-and-Data-Index-1"
href="#Function-and-Data-Index">Function and Data Index</a></li>
+<li><a name="stoc-Type-Index-1" href="#Type-Index">Type Index</a></li>
+</ul>
+</div>
+<hr size="1">
+<a name="SEC_About"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of
document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of
contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Concept-Index"
title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ?
</a>]</td>
+</tr></table>
+<h1>About This Document</h1>
<p>
+ This document was generated by <em>Christian Grothoff</em> on <em>January 8,
2010</em> using <a href="http://www.nongnu.org/texi2html/";><em>texi2html
1.82</em></a>.
+</p>
+<p>
+ The buttons in the navigation panels have the following meaning:
+</p>
+<table border="1">
+ <tr>
+ <th> Button </th>
+ <th> Name </th>
+ <th> Go to </th>
+ <th> From 1.2.3 go to</th>
+ </tr>
+ <tr>
+ <td align="center"> [ < ] </td>
+ <td align="center">Back</td>
+ <td>Previous section in reading order</td>
+ <td>1.2.2</td>
+ </tr>
+ <tr>
+ <td align="center"> [ > ] </td>
+ <td align="center">Forward</td>
+ <td>Next section in reading order</td>
+ <td>1.2.4</td>
+ </tr>
+ <tr>
+ <td align="center"> [ << ] </td>
+ <td align="center">FastBack</td>
+ <td>Beginning of this chapter or previous chapter</td>
+ <td>1</td>
+ </tr>
+ <tr>
+ <td align="center"> [ Up ] </td>
+ <td align="center">Up</td>
+ <td>Up section</td>
+ <td>1.2</td>
+ </tr>
+ <tr>
+ <td align="center"> [ >> ] </td>
+ <td align="center">FastForward</td>
+ <td>Next chapter</td>
+ <td>2</td>
+ </tr>
+ <tr>
+ <td align="center"> [Top] </td>
+ <td align="center">Top</td>
+ <td>Cover (top) of document</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td align="center"> [Contents] </td>
+ <td align="center">Contents</td>
+ <td>Table of contents</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td align="center"> [Index] </td>
+ <td align="center">Index</td>
+ <td>Index</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td align="center"> [ ? ] </td>
+ <td align="center">About</td>
+ <td>About (help)</td>
+ <td> </td>
+ </tr>
+</table>
+
+<p>
+ where the <strong> Example </strong> assumes that the current position is at
<strong> Subsubsection One-Two-Three </strong> of a document of the following
structure:
+</p>
+
+<ul>
+ <li> 1. Section One
+ <ul>
+ <li>1.1 Subsection One-One
+ <ul>
+ <li>...</li>
+ </ul>
+ </li>
+ <li>1.2 Subsection One-Two
+ <ul>
+ <li>1.2.1 Subsubsection One-Two-One</li>
+ <li>1.2.2 Subsubsection One-Two-Two</li>
+ <li>1.2.3 Subsubsection One-Two-Three
+ <strong><== Current Position </strong></li>
+ <li>1.2.4 Subsubsection One-Two-Four</li>
+ </ul>
+ </li>
+ <li>1.3 Subsection One-Three
+ <ul>
+ <li>...</li>
+ </ul>
+ </li>
+ <li>1.4 Subsection One-Four</li>
+ </ul>
+ </li>
+</ul>
+
+<hr size="1">
+<p>
<font size="-1">
- This document was generated by <em>Christian Grothoff</em> on <em>October,
11 2009</em> using <a href="http://www.nongnu.org/texi2html/";><em>texi2html
1.78</em></a>.
+ This document was generated by <em>Christian Grothoff</em> on <em>January 8,
2010</em> using <a href="http://www.nongnu.org/texi2html/";><em>texi2html
1.82</em></a>.
</font>
<br>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] r9966 - libmicrohttpd-docs/WWW,
gnunet <=