scsh-conservatory
/
sunet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

subtle change in description of httpd (forking a thread)

This commit is contained in:
interp 2002-04-03 18:06:43 +00:00
parent c816310cea
commit 3ce4729a91
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/latex/httpd.tex
View File

@ -74,18 +74,16 @@ one argument, a \ex{httpd\=options}-record:
\begin{desc}
This procedure starts the server. The various \semvar{options} can
be set via the options transformers that are explained below.
The server's basic loop is to wait on the port for a connection from
an HTTP client. When it receives a connection, it reads in and
parses the request into a special request data structure. Then the
server \FIXME{Does the server still fork or does it make a thread. Is
this a difference? (Do not know)} forks a child process, who binds
the current I/O ports to the connection socket, and then hands off
to the top-level \semvar{path-handler} (the first argument to
httpd). The \semvar{path-handler} procedure is responsible for
actually serving the request -- it can be any arbitrary computation.
Its output goes directly back to the HTTP client that sent the
request.
server forks a thread, who binds the current I/O ports to the
connection socket, and then hands off to the top-level
\semvar{path-handler} (the first argument to httpd). The
\semvar{path-handler} procedure is responsible for actually serving
the request -- it can be any arbitrary computation. Its output goes
directly back to the HTTP client that sent the request.
Before calling the path handler to service the request, the HTTP
server installs an error handler that fields any uncaught error,