Browse Source

Fix broken asciidoc section

v0.7.4-release
Ryan Dahl 16 years ago
parent
commit
69e8a01c58
  1. 5
      doc/api.html
  2. 4
      doc/api.txt
  3. 5
      doc/node.1

5
doc/api.html

@ -883,10 +883,11 @@ on error: no parameters.
</dt> </dt>
<dd> <dd>
<p> <p>
=== HTTP &#8230;
</p> </p>
</dd> </dd>
</dl></div> </dl></div>
<h3 id="_http">HTTP</h3><div style="clear:left"></div>
<div class="paragraph"><p>The HTTP interfaces in Node are designed to support many features <div class="paragraph"><p>The HTTP interfaces in Node are designed to support many features
of the protocol which have been traditionally difficult to use. of the protocol which have been traditionally difficult to use.
In particular, large, possibly chunk-encoded, messages. The interface is In particular, large, possibly chunk-encoded, messages. The interface is
@ -1862,7 +1863,7 @@ init (Handle&lt;Object&gt; target)
<div id="footer"> <div id="footer">
<div id="footer-text"> <div id="footer-text">
Version 0.1.10<br /> Version 0.1.10<br />
Last updated 2009-09-12 13:07:32 CEST Last updated 2009-09-12 19:12:41 CEST
</div> </div>
</div> </div>
</body> </body>

4
doc/api.txt

@ -534,7 +534,9 @@ Objects returned from +node.fs.stat()+ are of this type.
+stats.isFIFO()+:: +stats.isFIFO()+::
+stats.isSocket()+:: +stats.isSocket()+:: ...
=== HTTP === HTTP

5
doc/node.1

@ -780,8 +780,10 @@ Objects returned from node\.fs\.stat() are of this type\.
.PP .PP
stats\.isFile(), stats\.isDirectory(), stats\.isBlockDevice(), stats\.isCharacterDevice(), stats\.isSymbolicLink(), stats\.isFIFO(), stats\.isSocket() stats\.isFile(), stats\.isDirectory(), stats\.isBlockDevice(), stats\.isCharacterDevice(), stats\.isSymbolicLink(), stats\.isFIFO(), stats\.isSocket()
.RS 4 .RS 4
=== HTTP \&...
.RE .RE
.RE
.SS "HTTP"
The HTTP interfaces in Node are designed to support many features of the protocol which have been traditionally difficult to use\. In particular, large, possibly chunk\-encoded, messages\. The interface is careful to never buffer entire requests or responses\(emthe user is able to stream data\. The HTTP interfaces in Node are designed to support many features of the protocol which have been traditionally difficult to use\. In particular, large, possibly chunk\-encoded, messages\. The interface is careful to never buffer entire requests or responses\(emthe user is able to stream data\.
.sp .sp
HTTP message headers are represented by an object like this HTTP message headers are represented by an object like this
@ -798,7 +800,6 @@ HTTP message headers are represented by an object like this
.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\. 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
.sp .sp
.RE
.sp .sp
.it 1 an-trap .it 1 an-trap
.nr an-no-space-flag 1 .nr an-no-space-flag 1

Loading…
Cancel
Save