From: Ryan Dahl <ry@tinyclouds.org>
Date: Wed, 19 May 2010 18:01:21 +0000 (-0700)
Subject: Fix api for request.connection
X-Git-Tag: v0.1.96~15
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c489c2c1b57c547c1cda011aec3ffb4116985606;p=platform%2Fupstream%2Fnodejs.git

Fix api for request.connection
---

diff --git a/doc/api.markdown b/doc/api.markdown
index 732e8e0..9999148 100644
--- a/doc/api.markdown
+++ b/doc/api.markdown
@@ -1596,14 +1596,13 @@ This is an EventEmitter with the following events:
  `request` is an instance of `http.ServerRequest` and `response` is
  an instance of `http.ServerResponse`
 
-### Event: 'stream'
+### Event: 'connection'
 
 `function (stream) { }`
 
- When a new TCP stream is established.
- `stream` is an object of type `http.Connection`. Usually users
- will not want to access this event. The `stream` can also be
- accessed at `request.stream`.
+ When a new TCP stream is established. `stream` is an object of type
+ `net.Stream`. Usually users will not want to access this event. The
+ `stream` can also be accessed at `request.connection`.
 
 ### Event: 'close'
 
@@ -1784,7 +1783,9 @@ Resumes a paused request.
 
 The `net.Stream` object assocated with the connection.
 
-With HTTPS support, use request.connection.verifyPeer() and request.connection.getPeerCertificate() to obtain the client's authentication details.
+With HTTPS support, use request.connection.verifyPeer() and
+request.connection.getPeerCertificate() to obtain the client's
+authentication details.
 
 
 ## http.ServerResponse