commit 13941d3b7f0e644457e14f7fcaceb25918223c16
parent ee6c58eb66cc1dbc9086d9fd925acf059096829e
Author: Christian Grothoff <christian@grothoff.org>
Date: Wed, 13 Aug 2008 17:20:43 +0000
edits
Diffstat:
4 files changed, 18 insertions(+), 20 deletions(-)
diff --git a/doc/Makefile.am b/doc/Makefile.am
@@ -1,7 +1,7 @@
man_MANS = libmicrohttpd.3
EXTRA_DIST = $(man_MANS) Doxyfile
-DISTCLEANFILES = microhttpd.cps
-info_TEXINFOS = microhttpd.texi
-microhttpd_TEXINFOS = lgpl.texi
+DISTCLEANFILES = microhttpd.cps tutorial.cps
+info_TEXINFOS = microhttpd.texi tutorial.texi
+microhttpd_TEXINFOS = lgpl.texi basicauthentication.inc bibliography.inc exploringrequests.inc fdl-1.2.texi hellobrowser.inc introduction.inc processingpost.inc responseheaders.inc
diff --git a/doc/hellobrowser.inc b/doc/hellobrowser.inc
@@ -1,5 +1,5 @@
The most basic task for a HTTP server is to deliver a static text message to any client connecting to it.
-Given that this is also very easy to implement, it is an excellent problem to start with.
+Given that this is also easy to implement, it is an excellent problem to start with.
For now, the particular filename the client asks for shall have no effect on the message that will
be returned. In addition, the server shall end the connection after the message has been sent so that
diff --git a/doc/introduction.inc b/doc/introduction.inc
@@ -1,19 +1,17 @@
-This tutorial is aimed at developers who want to learn how they can add HTTP serving
+This tutorial is for developers who want to learn how they can add HTTP serving
capabilities to their applications with the @emph{GNU libmicrohttpd} library,
-abbreviated @emph{MHD}, and who do not know how to start. It tries to help these
-developers to implement common basic HTTP serving tasks by discussing executable
-sample programs implementing different features.
+abbreviated @emph{MHD}. The reader will learn how to
+implement basic HTTP functions from simple executable
+sample programs that implement various features.
The text is supposed to be a supplement to the API reference manual of
@emph{GNU libmicrohttpd} and for that reason does not explain many of the parameters.
Therefore, the reader should always consult the manual to find the exact meaning
-of the functions used in the tutorial. In the same sense, the tutorial seeks to
-encourage the use of the @emph{RFCs}, which document the conventions the Internet
-is built upon.
+of the functions used in the tutorial. Furthermore, the reader is
+encouraged to study the relevant @emph{RFCs}, which document the HTTP standard.
-@emph{GNU libmicrohttpd} is assumed to be already installed and it has been
-written with respect to version @value{VERSION}. As the library is still in its
-beta stages, later versions may show different behaviour. At the time being,
+@emph{GNU libmicrohttpd} is assumed to be already installed. This tutorial
+is written for version @value{VERSION}. At the time being,
this tutorial has only been tested on @emph{GNU/Linux} machines even though
efforts were made not to rely on anything that would prevent the samples from being
built on similar systems.
diff --git a/doc/tutorial.texi b/doc/tutorial.texi
@@ -36,8 +36,8 @@ Free Documentation License".
* Hello browser example::
* Exploring requests::
* Response headers::
-* A basic authentication::
-* Processing post data::
+* Supporting basic authentication::
+* Processing POST data::
* Bibliography::
* License text::
* Example programs::
@@ -59,12 +59,12 @@ Free Documentation License".
@chapter Response headers
@include responseheaders.inc
-@node A basic authentication
-@chapter A basic authentication
+@node Supporting basic authentication
+@chapter Supporting basic authentication
@include basicauthentication.inc
-@node Processing post data
-@chapter Processing post data
+@node Processing POST data
+@chapter Processing POST data
@include processingpost.inc
