-*- org -*-
* Notes
-* Tasks [8/9]
+* Tasks [8/10]
+** TODO documentation for running in a chroot jail
+see https://wiki.archlinux.org/index.php/nginx#Installation_in_a_chroot
+
** incremental handler calls
not sure if the extra performance is worth the added complexity
--- /dev/null
+This is the file .../info/dir, which contains the
+topmost node of the Info hierarchy, called (dir)Top.
+The first time you invoke Info you start off looking at this node.
+\1f
+File: dir, Node: Top This is the top of the INFO tree
+
+ This (the Directory node) gives a menu of major topics.
+ Typing "q" exits, "?" lists all Info commands, "d" returns here,
+ "h" gives a primer for first-timers,
+ "mEmacs<Return>" visits the Emacs manual, etc.
+
+ In Emacs, you can click mouse button 2 on a menu item or cross reference
+ to select it.
+
+* Menu:
+
+Emacs
+* Web Server: (web-server). Web server running Emacs Lisp handlers
Lisp. HTTP requests are matched to handlers (@pxref{Handlers}) which
are Emacs Lisp functions. Handlers receive as their only argument a
request object (@pxref{Requests}) which holds information about the
-request and the process holding HTTP network connection. Handlers
+request and a process holding the HTTP network connection. Handlers
write their responses directly to the network process.
A number of examples (@pxref{Usage Examples}) demonstrate usage of the
This example demonstrates access of URL-encoded parameters in a
@code{GET} request. For example the following URL
-@url{http://localhost:9005/example?foo=bar&baz=qux} will render as an
+@url{http://localhost:9005/example?foo=bar&baz=qux} will render as
the following HTML table.
@multitable @columnfractions .5 .5