<entryalign="left"valign="top"><simpara>Identical to the <literal>"output"</literal> event except for <literal>stderr</literal> instead of <literal>stdout</literal>.</simpara></entry>
<entryalign="left"valign="top"><simpara>Identical to the <literal>"output"</literal> event except for
<literal>stderr</literal> instead of <literal>stdout</literal>.</simpara></entry>
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\.
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
.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
.sp
Functions can be then be attached to objects, to be executed when an event is emitted\. These functions are called \fIlisteners\fR\.
Functions can be then be attached to objects, to be executed when an event is emitted\. These functions are called \fIlisteners\fR\.
.sp
.sp
@ -519,7 +519,7 @@ T}:T{
data
data
.sp
.sp
T}:T{
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
.sp
T}
T}
T{
T{
@ -847,7 +847,7 @@ HTTP message headers are represented by an object like this
}
}
.fi
.fi
.RE
.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
.sp
.sp
.it1an-trap
.it1an-trap
@ -967,6 +967,7 @@ T{
"complete"
"complete"
.sp
.sp
T}:T{
T}:T{
(none)
.sp
.sp
T}:T{
T}:T{
Emitted exactly once for each message\. No arguments\. After emitted no other events will be emitted on the request\.
Emitted exactly once for each message\. No arguments\. After emitted no other events will be emitted on the request\.
@ -988,7 +989,7 @@ Request URI Object\. This contains only the parameters that are present in the a
.RS4
.RS4
.nf
.nf
GET /status?name=ryan HTTP/1\.1\er\en
GET /status?name=ryan HTTP/1\.1\er\en
Accept: */*\er\en
Accept: text/plain\er\en
\er\en
\er\en
.fi
.fi
.RE
.RE
@ -1010,6 +1011,7 @@ request\.uri\.protocol
is
is
undefined\. This is because there was no URI protocol given in the actual HTTP Request\.
undefined\. This is because there was no URI protocol given in the actual HTTP Request\.
Ryan Dahl
15 years ago