<div class="paragraph"><p>Many objects in Node emit events: a TCP server emits an event each time\r
there is a connection, a child process emits an event when it exits. All\r
objects which emit events are are instances of <tt>node.EventEmitter</tt>.</p></div>\r
-<div class="paragraph"><p>Events are represented by a snakecased string. Here are some examples:\r
-<tt>"connection"</tt>, <tt>"receive"</tt>, <tt>"message_begin"</tt>.</p></div>\r
+<div class="paragraph"><p>Events are represented by a camel-cased string. Here are some examples:\r
+<tt>"connection"</tt>, <tt>"receive"</tt>, <tt>"messageBegin"</tt>.</p></div>\r
<div class="paragraph"><p>Functions can be then be attached to objects, to be executed when an event\r
is emitted. These functions are called <em>listeners</em>.</p></div>\r
<div class="paragraph"><p>Some asynchronous file operations return an <tt>EventEmitter</tt> called a\r
<col width="76%" />\r
<thead>\r
<tr>\r
-<th align="left" valign="top">Event </th>\r
-<th align="left" valign="top">Parameters </th>\r
+<th align="left" valign="top"> Event </th>\r
+<th align="left" valign="top"> Parameters </th>\r
<th align="left" valign="top">Notes</th>\r
</tr>\r
</thead>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"output"</tt></p></td>\r
<td align="left" valign="top"><p class="table"><tt>data</tt></p></td>\r
-<td align="left" valign="top"><p class="table">Each time the child process sends data to its <tt>stdout</tt>, this event is\r
-emitted. <tt>data</tt> is a string.<br />\r
-If the child process closes its <tt>stdout</tt> stream (a common thing to do on\r
-exit), this event will be emitted with <tt>data === null</tt>.</p></td>\r
+<td align="left" valign="top"><p class="table">Each time the child process\r
+ sends data to its <tt>stdout</tt>, this event is\r
+ emitted. <tt>data</tt> is a string. + If the child\r
+ process closes its <tt>stdout</tt> stream (a common\r
+ thing to do on exit), this event will be emitted\r
+ with <tt>data === null</tt>.</p></td>\r
</tr>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"error"</tt></p></td>\r
<td align="left" valign="top"><p class="table"><tt>data</tt></p></td>\r
-<td align="left" valign="top"><p class="table">Identical to the <tt>"output"</tt> event except for <tt>stderr</tt> instead of <tt>stdout</tt>.</p></td>\r
+<td align="left" valign="top"><p class="table">Identical to the <tt>"output"</tt> event except for\r
+ <tt>stderr</tt> instead of <tt>stdout</tt>.</p></td>\r
</tr>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"exit"</tt></p></td>\r
<td align="left" valign="top"><p class="table"><tt>code</tt></p></td>\r
-<td align="left" valign="top"><p class="table">This event is emitted after the child process ends. <tt>code</tt> is the final exit\r
-code of the process. One can be assured that after this event is emitted\r
-that the <tt>"output"</tt> and <tt>"error"</tt> callbacks will no longer be made.</p></td>\r
+<td align="left" valign="top"><p class="table">This event is emitted after the child process\r
+ ends. <tt>code</tt> is the final exit code of the\r
+ process. One can be assured that after this\r
+ event is emitted that the <tt>"output"</tt> and\r
+ <tt>"error"</tt> callbacks will no longer be made.</p></td>\r
</tr>\r
</tbody>\r
</table>\r
<div class="paragraph"><p>In order to support the full spectrum of possible HTTP applications, Node’s\r
HTTP API is very low-level. It deals with connection handling and message\r
parsing only. It parses a message into headers and body but it does not\r
-parse the actual headers or the body. That means, for example, that Node\r
-does not, and will never, provide API to access or manipulate Cookies or\r
-multi-part bodies. <em>This is left to the user.</em></p></div>\r
+parse the actual headers or the body.</p></div>\r
<h4 id="_tt_http_server_tt"><tt>http.Server</tt></h4>\r
<div class="tableblock">\r
<table rules="all"\r
<thead>\r
<tr>\r
<th align="left" valign="top">Event </th>\r
-<th align="left" valign="top"> Parameters </th>\r
+<th align="left" valign="top"> Parameters </th>\r
<th align="left" valign="top"> Notes</th>\r
</tr>\r
</thead>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"request"</tt></p></td>\r
<td align="left" valign="top"><p class="table"><tt>request, response</tt></p></td>\r
-<td align="left" valign="top"><p class="table"><tt>request</tt> is an instance of <tt>http.ServerRequest</tt><br />\r
-<tt>response</tt> is an instance of <tt>http.ServerResponse</tt></p></td>\r
+<td align="left" valign="top"><p class="table"><tt>request</tt> is an instance of <tt>http.ServerRequest</tt>\r
+ <br />\r
+ <tt>response</tt> is an instance of <tt>http.ServerResponse</tt></p></td>\r
</tr>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"connection"</tt></p></td>\r
<td align="left" valign="top"><p class="table"><tt>connection</tt></p></td>\r
<td align="left" valign="top"><p class="table">When a new TCP connection is established.\r
-<tt>connection</tt> is an object of type <tt>http.Connection</tt>. Usually users will not\r
-want to access this event. The <tt>connection</tt> can also be accessed at\r
-<tt>request.connection</tt>.</p></td>\r
+ <tt>connection</tt> is an object of type\r
+ <tt>http.Connection</tt>. Usually users\r
+ will not want to access this event.\r
+ The <tt>connection</tt> can also be\r
+ accessed at <tt>request.connection</tt>.</p></td>\r
</tr>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"close"</tt></p></td>\r
<td align="left" valign="top"><p class="table"><tt>errorno</tt></p></td>\r
<td align="left" valign="top"><p class="table">Emitted when the server closes. <tt>errorno</tt>\r
- is an integer which indicates what, if any,\r
- error caused the server to close. If no\r
- error occured <tt>errorno</tt> will be 0.</p></td>\r
+ is an integer which indicates what, if any,\r
+ error caused the server to close. If no\r
+ error occured <tt>errorno</tt> will be 0.</p></td>\r
</tr>\r
</tbody>\r
</table>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"body"</tt></p></td>\r
<td align="left" valign="top"><p class="table"><tt>chunk</tt></p></td>\r
-<td align="left" valign="top"><p class="table">Emitted when a piece of the message body is received. Example: A chunk of\r
-the body is given as the single argument. The transfer-encoding has been\r
-decoded. The body chunk is a String. The body encoding is set\r
-with <tt>request.setBodyEncoding()</tt>.</p></td>\r
+<td align="left" valign="top"><p class="table">Emitted when a piece of the\r
+ message body is received. Example: A chunk\r
+ of the body is given as the single\r
+ argument. The transfer-encoding has been\r
+ decoded. The body chunk is a String. The\r
+ body encoding is set with\r
+ <tt>request.setBodyEncoding()</tt>.</p></td>\r
</tr>\r
<tr>\r
<td align="left" valign="top"><p class="table"><tt>"complete"</tt></p></td>\r
-<td align="left" valign="top"><p class="table"></p></td>\r
-<td align="left" valign="top"><p class="table">Emitted exactly once for each message. No arguments.\r
-After emitted no other events will be emitted on the request.</p></td>\r
+<td align="left" valign="top"><p class="table">(none)</p></td>\r
+<td align="left" valign="top"><p class="table">Emitted exactly once for each message.\r
+ No arguments. After emitted no other\r
+ events will be emitted on the request.</p></td>\r
</tr>\r
</tbody>\r
</table>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>GET /status?name=ryan HTTP/1.1\r\n\r
-Accept: */*\r\n\r
+Accept: text/plain\r\n\r
\r\n</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>Then <tt>request.uri</tt> will be</p></div>\r
<div class="paragraph"><p>In particular, note that <tt>request.uri.protocol</tt> is\r
<tt>undefined</tt>. This is because there was no URI protocol given\r
in the actual HTTP Request.</p></div>\r
-<div class="paragraph"><p><tt>request.uri.anchor</tt>, <tt>request.uri.query</tt>, <tt>request.uri.file</tt>, <tt>request.uri.directory</tt>, <tt>request.uri.path</tt>, <tt>request.uri.relative</tt>, <tt>request.uri.port</tt>, <tt>request.uri.host</tt>, <tt>request.uri.password</tt>, <tt>request.uri.user</tt>, <tt>request.uri.authority</tt>, <tt>request.uri.protocol</tt>, <tt>request.uri.params</tt>, <tt>request.uri.toString()</tt>, <tt>request.uri.source</tt></p></div>\r
+<div class="paragraph"><p>Here is what’s available: <tt>request.uri.anchor</tt>, <tt>request.uri.query</tt>,\r
+<tt>request.uri.file</tt>, <tt>request.uri.directory</tt>, <tt>request.uri.path</tt>,\r
+<tt>request.uri.relative</tt>, <tt>request.uri.port</tt>, <tt>request.uri.host</tt>,\r
+<tt>request.uri.password</tt>, <tt>request.uri.user</tt>, <tt>request.uri.authority</tt>,\r
+<tt>request.uri.protocol</tt>, <tt>request.uri.params</tt>, <tt>request.uri.toString()</tt>,\r
+<tt>request.uri.source</tt></p></div>\r
</dd>\r
<dt class="hdlist1">\r
<tt>request.headers</tt> \r
<div id="footer">\r
<div id="footer-text">\r
Version 0.1.12<br />\r
-Last updated 2009-09-28 21:50:11 CEST\r
+Last updated 2009-09-29 09:59:52 CEST\r
</div>\r
</div>\r
</body>\r
there is a connection, a child process emits an event when it exits. All
objects which emit events are are instances of +node.EventEmitter+.
-Events are represented by a snakecased string. Here are some examples:
-+"connection"+, +"receive"+, +"message_begin"+.
+Events are represented by a camel-cased string. Here are some examples:
++"connection"+, +"receive"+, +"messageBegin"+.
Functions can be then be attached to objects, to be executed when an event
is emitted. These functions are called _listeners_.
[cols="1,2,10",options="header"]
|=========================================================
-|Event |Parameters |Notes
-
-|+"output"+ | +data+ |
-Each time the child process sends data to its +stdout+, this event is
-emitted. +data+ is a string.
-+
-If the child process closes its +stdout+ stream (a common thing to do on
-exit), this event will be emitted with +data === null+.
-
-
-|+"error"+ | +data+ |
-Identical to the +"output"+ event except for +stderr+ instead of +stdout+.
-
-|+"exit"+ | +code+ |
-This event is emitted after the child process ends. +code+ is the final exit
-code of the process. One can be assured that after this event is emitted
-that the +"output"+ and +"error"+ callbacks will no longer be made.
-
+| Event | Parameters |Notes
+
+| +"output"+ | +data+ | Each time the child process
+ sends data to its +stdout+, this event is
+ emitted. +data+ is a string. + If the child
+ process closes its +stdout+ stream (a common
+ thing to do on exit), this event will be emitted
+ with +data === null+.
+
+| +"error"+ | +data+ | Identical to the +"output"+ event except for
+ +stderr+ instead of +stdout+.
+
+| +"exit"+ | +code+ | This event is emitted after the child process
+ ends. +code+ is the final exit code of the
+ process. One can be assured that after this
+ event is emitted that the +"output"+ and
+ +"error"+ callbacks will no longer be made.
|=========================================================
+node.createChildProcess(command)+::
In order to support the full spectrum of possible HTTP applications, Node's
HTTP API is very low-level. It deals with connection handling and message
parsing only. It parses a message into headers and body but it does not
-parse the actual headers or the body. That means, for example, that Node
-does not, and will never, provide API to access or manipulate Cookies or
-multi-part bodies. _This is left to the user._
+parse the actual headers or the body.
==== +http.Server+
[cols="1,2,10",options="header"]
|=========================================================
-|Event | Parameters | Notes
+|Event | Parameters | Notes
-|+"request"+ | +request, response+ |
-+request+ is an instance of +http.ServerRequest+
-+
-+response+ is an instance of +http.ServerResponse+
+|+"request"+ | +request, response+ | +request+ is an instance of +http.ServerRequest+
+ +
+ +response+ is an instance of +http.ServerResponse+
-|+"connection"+ | +connection+ |
-When a new TCP connection is established.
-+connection+ is an object of type +http.Connection+. Usually users will not
-want to access this event. The +connection+ can also be accessed at
-+request.connection+.
+|+"connection"+ | +connection+ | When a new TCP connection is established.
+ +connection+ is an object of type
+ +http.Connection+. Usually users
+ will not want to access this event.
+ The +connection+ can also be
+ accessed at +request.connection+.
-|+"close"+ | +errorno+ | Emitted when the server closes. +errorno+
- is an integer which indicates what, if any,
- error caused the server to close. If no
- error occured +errorno+ will be 0.
+|+"close"+ | +errorno+ | Emitted when the server closes. +errorno+
+ is an integer which indicates what, if any,
+ error caused the server to close. If no
+ error occured +errorno+ will be 0.
|=========================================================
|=========================================================
|Event | Parameters | Notes
-|+"body"+ | +chunk+ |
-Emitted when a piece of the message body is received. Example: A chunk of
-the body is given as the single argument. The transfer-encoding has been
-decoded. The body chunk is a String. The body encoding is set
-with +request.setBodyEncoding()+.
-
-|+"complete"+ | |
-Emitted exactly once for each message. No arguments.
-After emitted no other events will be emitted on the request.
-
+|+"body"+ | +chunk+ | Emitted when a piece of the
+ message body is received. Example: A chunk
+ of the body is given as the single
+ argument. The transfer-encoding has been
+ decoded. The body chunk is a String. The
+ body encoding is set with
+ +request.setBodyEncoding()+.
+
+|+"complete"+ | (none) | Emitted exactly once for each message.
+ No arguments. After emitted no other
+ events will be emitted on the request.
|=========================================================
+request.method+ ::
+
----------------------------------------
GET /status?name=ryan HTTP/1.1\r\n
-Accept: */*\r\n
+Accept: text/plain\r\n
\r\n
----------------------------------------
+
+undefined+. This is because there was no URI protocol given
in the actual HTTP Request.
+
-+request.uri.anchor+, +request.uri.query+, +request.uri.file+, +request.uri.directory+, +request.uri.path+, +request.uri.relative+, +request.uri.port+, +request.uri.host+, +request.uri.password+, +request.uri.user+, +request.uri.authority+, +request.uri.protocol+, +request.uri.params+, +request.uri.toString()+, +request.uri.source+
+Here is what's available: +request.uri.anchor+, +request.uri.query+,
++request.uri.file+, +request.uri.directory+, +request.uri.path+,
++request.uri.relative+, +request.uri.port+, +request.uri.host+,
++request.uri.password+, +request.uri.user+, +request.uri.authority+,
++request.uri.protocol+, +request.uri.params+, +request.uri.toString()+,
++request.uri.source+
+request.headers+ ::
<simpara>Many objects in Node emit events: a TCP server emits an event each time\r
there is a connection, a child process emits an event when it exits. All\r
objects which emit events are are instances of <literal>node.EventEmitter</literal>.</simpara>\r
-<simpara>Events are represented by a snakecased string. Here are some examples:\r
-<literal>"connection"</literal>, <literal>"receive"</literal>, <literal>"message_begin"</literal>.</simpara>\r
+<simpara>Events are represented by a camel-cased string. Here are some examples:\r
+<literal>"connection"</literal>, <literal>"receive"</literal>, <literal>"messageBegin"</literal>.</simpara>\r
<simpara>Functions can be then be attached to objects, to be executed when an event\r
is emitted. These functions are called <emphasis>listeners</emphasis>.</simpara>\r
<simpara>Some asynchronous file operations return an <literal>EventEmitter</literal> called a\r
<colspec colname="col_3" colwidth="76*"/>\r
<thead>\r
<row>\r
-<entry align="left" valign="top">Event </entry>\r
-<entry align="left" valign="top">Parameters </entry>\r
+<entry align="left" valign="top"> Event </entry>\r
+<entry align="left" valign="top"> Parameters </entry>\r
<entry align="left" valign="top">Notes</entry>\r
</row>\r
</thead>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"output"</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara><literal>data</literal></simpara></entry>\r
-<entry align="left" valign="top"><simpara>Each time the child process sends data to its <literal>stdout</literal>, this event is\r
-emitted. <literal>data</literal> is a string.<?asciidoc-br?>\r
-If the child process closes its <literal>stdout</literal> stream (a common thing to do on\r
-exit), this event will be emitted with <literal>data === null</literal>.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Each time the child process\r
+ sends data to its <literal>stdout</literal>, this event is\r
+ emitted. <literal>data</literal> is a string. + If the child\r
+ process closes its <literal>stdout</literal> stream (a common\r
+ thing to do on exit), this event will be emitted\r
+ with <literal>data === null</literal>.</simpara></entry>\r
</row>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"error"</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara><literal>data</literal></simpara></entry>\r
-<entry align="left" valign="top"><simpara>Identical to the <literal>"output"</literal> event except for <literal>stderr</literal> instead of <literal>stdout</literal>.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Identical to the <literal>"output"</literal> event except for\r
+ <literal>stderr</literal> instead of <literal>stdout</literal>.</simpara></entry>\r
</row>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"exit"</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara><literal>code</literal></simpara></entry>\r
-<entry align="left" valign="top"><simpara>This event is emitted after the child process ends. <literal>code</literal> is the final exit\r
-code of the process. One can be assured that after this event is emitted\r
-that the <literal>"output"</literal> and <literal>"error"</literal> callbacks will no longer be made.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>This event is emitted after the child process\r
+ ends. <literal>code</literal> is the final exit code of the\r
+ process. One can be assured that after this\r
+ event is emitted that the <literal>"output"</literal> and\r
+ <literal>"error"</literal> callbacks will no longer be made.</simpara></entry>\r
</row>\r
</tbody>\r
</tgroup>\r
<simpara>In order to support the full spectrum of possible HTTP applications, Node’s\r
HTTP API is very low-level. It deals with connection handling and message\r
parsing only. It parses a message into headers and body but it does not\r
-parse the actual headers or the body. That means, for example, that Node\r
-does not, and will never, provide API to access or manipulate Cookies or\r
-multi-part bodies. <emphasis>This is left to the user.</emphasis></simpara>\r
+parse the actual headers or the body.</simpara>\r
<refsect3 id="_literal_http_server_literal">\r
<title><literal>http.Server</literal></title>\r
<informaltable\r
<thead>\r
<row>\r
<entry align="left" valign="top">Event </entry>\r
-<entry align="left" valign="top"> Parameters </entry>\r
+<entry align="left" valign="top"> Parameters </entry>\r
<entry align="left" valign="top"> Notes</entry>\r
</row>\r
</thead>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"request"</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara><literal>request, response</literal></simpara></entry>\r
-<entry align="left" valign="top"><simpara><literal>request</literal> is an instance of <literal>http.ServerRequest</literal><?asciidoc-br?>\r
-<literal>response</literal> is an instance of <literal>http.ServerResponse</literal></simpara></entry>\r
+<entry align="left" valign="top"><simpara><literal>request</literal> is an instance of <literal>http.ServerRequest</literal>\r
+ <?asciidoc-br?>\r
+ <literal>response</literal> is an instance of <literal>http.ServerResponse</literal></simpara></entry>\r
</row>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"connection"</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara><literal>connection</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara>When a new TCP connection is established.\r
-<literal>connection</literal> is an object of type <literal>http.Connection</literal>. Usually users will not\r
-want to access this event. The <literal>connection</literal> can also be accessed at\r
-<literal>request.connection</literal>.</simpara></entry>\r
+ <literal>connection</literal> is an object of type\r
+ <literal>http.Connection</literal>. Usually users\r
+ will not want to access this event.\r
+ The <literal>connection</literal> can also be\r
+ accessed at <literal>request.connection</literal>.</simpara></entry>\r
</row>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"close"</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara><literal>errorno</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara>Emitted when the server closes. <literal>errorno</literal>\r
- is an integer which indicates what, if any,\r
- error caused the server to close. If no\r
- error occured <literal>errorno</literal> will be 0.</simpara></entry>\r
+ is an integer which indicates what, if any,\r
+ error caused the server to close. If no\r
+ error occured <literal>errorno</literal> will be 0.</simpara></entry>\r
</row>\r
</tbody>\r
</tgroup>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"body"</literal></simpara></entry>\r
<entry align="left" valign="top"><simpara><literal>chunk</literal></simpara></entry>\r
-<entry align="left" valign="top"><simpara>Emitted when a piece of the message body is received. Example: A chunk of\r
-the body is given as the single argument. The transfer-encoding has been\r
-decoded. The body chunk is a String. The body encoding is set\r
-with <literal>request.setBodyEncoding()</literal>.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Emitted when a piece of the\r
+ message body is received. Example: A chunk\r
+ of the body is given as the single\r
+ argument. The transfer-encoding has been\r
+ decoded. The body chunk is a String. The\r
+ body encoding is set with\r
+ <literal>request.setBodyEncoding()</literal>.</simpara></entry>\r
</row>\r
<row>\r
<entry align="left" valign="top"><simpara><literal>"complete"</literal></simpara></entry>\r
-<entry align="left" valign="top"><simpara></simpara></entry>\r
-<entry align="left" valign="top"><simpara>Emitted exactly once for each message. No arguments.\r
-After emitted no other events will be emitted on the request.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>(none)</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Emitted exactly once for each message.\r
+ No arguments. After emitted no other\r
+ events will be emitted on the request.</simpara></entry>\r
</row>\r
</tbody>\r
</tgroup>\r
present in the actual HTTP request. That is, if the request is\r
</simpara>\r
<screen>GET /status?name=ryan HTTP/1.1\r\n\r
-Accept: */*\r\n\r
+Accept: text/plain\r\n\r
\r\n</screen>\r
<simpara>Then <literal>request.uri</literal> will be</simpara>\r
<screen>{ path: "/status",\r
<simpara>In particular, note that <literal>request.uri.protocol</literal> is\r
<literal>undefined</literal>. This is because there was no URI protocol given\r
in the actual HTTP Request.</simpara>\r
-<simpara><literal>request.uri.anchor</literal>, <literal>request.uri.query</literal>, <literal>request.uri.file</literal>, <literal>request.uri.directory</literal>, <literal>request.uri.path</literal>, <literal>request.uri.relative</literal>, <literal>request.uri.port</literal>, <literal>request.uri.host</literal>, <literal>request.uri.password</literal>, <literal>request.uri.user</literal>, <literal>request.uri.authority</literal>, <literal>request.uri.protocol</literal>, <literal>request.uri.params</literal>, <literal>request.uri.toString()</literal>, <literal>request.uri.source</literal></simpara>\r
+<simpara>Here is what’s available: <literal>request.uri.anchor</literal>, <literal>request.uri.query</literal>,\r
+<literal>request.uri.file</literal>, <literal>request.uri.directory</literal>, <literal>request.uri.path</literal>,\r
+<literal>request.uri.relative</literal>, <literal>request.uri.port</literal>, <literal>request.uri.host</literal>,\r
+<literal>request.uri.password</literal>, <literal>request.uri.user</literal>, <literal>request.uri.authority</literal>,\r
+<literal>request.uri.protocol</literal>, <literal>request.uri.params</literal>, <literal>request.uri.toString()</literal>,\r
+<literal>request.uri.source</literal></simpara>\r
</listitem>\r
</varlistentry>\r
<varlistentry>\r
.\" Title: node
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
-.\" Date: 09/28/2009
+.\" Date: 09/29/2009
.\" Manual:
.\" Source:
.\"
-.TH "NODE" "1" "09/28/2009" "" ""
+.TH "NODE" "1" "09/29/2009" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SS "Events"
Many objects in Node emit events: a TCP server emits an event each time there is a connection, a child process emits an event when it exits\. All objects which emit events are are instances of node\.EventEmitter\.
.sp
-Events are represented by a snakecased string\. Here are some examples: "connection", "receive", "message_begin"\.
+Events are represented by a camel\-cased string\. Here are some examples: "connection", "receive", "messageBegin"\.
.sp
Functions can be then be attached to objects, to be executed when an event is emitted\. These functions are called \fIlisteners\fR\.
.sp
data
.sp
T}:T{
-Each time the child process sends data to its stdout, this event is emitted\. data is a string\. If the child process closes its stdout stream (a common thing to do on exit), this event will be emitted with data === null\.
+Each time the child process sends data to its stdout, this event is emitted\. data is a string\. + If the child process closes its stdout stream (a common thing to do on exit), this event will be emitted with data === null\.
.sp
T}
T{
}
.fi
.RE
-In order to support the full spectrum of possible HTTP applications, Node\(cqs HTTP API is very low\-level\. It deals with connection handling and message parsing only\. It parses a message into headers and body but it does not parse the actual headers or the body\. That means, for example, that Node does not, and will never, provide API to access or manipulate Cookies or multi\-part bodies\. \fIThis is left to the user\.\fR
+In order to support the full spectrum of possible HTTP applications, Node\(cqs HTTP API is very low\-level\. It deals with connection handling and message parsing only\. It parses a message into headers and body but it does not parse the actual headers or the body\.
.sp
.sp
.it 1 an-trap
"complete"
.sp
T}:T{
+(none)
.sp
T}:T{
Emitted exactly once for each message\. No arguments\. After emitted no other events will be emitted on the request\.
.RS 4
.nf
GET /status?name=ryan HTTP/1\.1\er\en
-Accept: */*\er\en
+Accept: text/plain\er\en
\er\en
.fi
.RE
is
undefined\. This is because there was no URI protocol given in the actual HTTP Request\.
.sp
+Here is what\(cqs available:
request\.uri\.anchor,
request\.uri\.query,
request\.uri\.file,
projects / platform / upstream / nodejs.git / commitdiff