gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] r17976 - in libmicrohttpd: . doc doc/chapters


From: gnunet
Subject: [GNUnet-SVN] r17976 - in libmicrohttpd: . doc doc/chapters
Date: Fri, 4 Nov 2011 10:03:24 +0100

Author: grothoff
Date: 2011-11-04 10:03:24 +0100 (Fri, 04 Nov 2011)
New Revision: 17976

Modified:
   libmicrohttpd/ChangeLog
   libmicrohttpd/doc/chapters/hellobrowser.inc
   libmicrohttpd/doc/microhttpd-tutorial.texi
Log:
docu

Modified: libmicrohttpd/ChangeLog
===================================================================
--- libmicrohttpd/ChangeLog     2011-11-04 01:00:45 UTC (rev 17975)
+++ libmicrohttpd/ChangeLog     2011-11-04 09:03:24 UTC (rev 17976)
@@ -1,3 +1,6 @@
+Fri Nov  4 10:03:00 CET 2011
+       Small updates to the tutorial. -CG
+
 Thu Nov  3 10:14:59 CET 2011
        shutdown(RDWR) fails on OS X after shutdown(RD), so only use
        shutdown(WR) if we already closed the socket for reading (otherwise

Modified: libmicrohttpd/doc/chapters/hellobrowser.inc
===================================================================
--- libmicrohttpd/doc/chapters/hellobrowser.inc 2011-11-04 01:00:45 UTC (rev 
17975)
+++ libmicrohttpd/doc/chapters/hellobrowser.inc 2011-11-04 09:03:24 UTC (rev 
17976)
@@ -155,12 +155,17 @@
 @code{MHD_NO} if not so.
 
 Secondly, the above practice of queuing a response upon the first call of the 
callback function
-brings with it some limitations. This is because the content of the message 
body will not be
-received if a response is queued in the first iteration. Furthermore, the 
connection will be closed
-right after the response has been transferred then.
+brings with it some limitations.  This is because the content of the message 
body will not be
+received if a response is queued in the first iteration.  Furthermore, the 
connection will be closed
+right after the response has been transferred then.  This is typically not 
what you want as it
+disables HTTP pipelining.  The correct approach is to simply not queue a 
message on the first
+callback unless there is an error.  The @code{void**} argument to the callback 
provides a location
+for storing information about the history of the connection; for the first 
call, the pointer
+will point to NULL.  A simplistic way to differenciate the first call from 
others is to check
+if the pointer is NULL and set it to a non-NULL value during the first call.
 
 Both of these issues you will find addressed in the official 
@code{minimal_example.c} residing in
-the @code{src/examples} directory of the @emph{MHD} package. The source code 
of this
+the @code{src/examples} directory of the @emph{MHD} package.  The source code 
of this
 program should look very familiar to you by now and easy to understand.
 
 For our example, the @code{must_copy} and @code{must_free} parameter at the 
response construction

Modified: libmicrohttpd/doc/microhttpd-tutorial.texi
===================================================================
--- libmicrohttpd/doc/microhttpd-tutorial.texi  2011-11-04 01:00:45 UTC (rev 
17975)
+++ libmicrohttpd/doc/microhttpd-tutorial.texi  2011-11-04 09:03:24 UTC (rev 
17976)
@@ -1,10 +1,10 @@
 \input texinfo  @c -*-texinfo-*-
 @finalout
 @setfilename microhttpd-tutorial.info
address@hidden UPDATED 28 Feb 2010
address@hidden UPDATED-MONTH Feb 2010
address@hidden EDITION 0.9.8
address@hidden VERSION 0.9.8
address@hidden UPDATED 2 Nov 2011
address@hidden UPDATED-MONTH Nov 2011
address@hidden EDITION 0.9.16
address@hidden VERSION 0.9.16
 @settitle A tutorial for GNU libmicrohttpd
 
 @dircategory GNU Libraries




reply via email to

[Prev in Thread] Current Thread [Next in Thread]