You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ig...@apache.org on 2011/01/07 17:09:07 UTC

svn commit: r1056369 - /trafficserver/site/trunk/docs/v2/sdk/IOGuide.html

Author: igalic
Date: Fri Jan  7 16:09:06 2011
New Revision: 1056369

URL: http://svn.apache.org/viewvc?rev=1056369&view=rev
Log:
zwoop: It's a big number ;)

Modified:
    trafficserver/site/trunk/docs/v2/sdk/IOGuide.html

Modified: trafficserver/site/trunk/docs/v2/sdk/IOGuide.html
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/docs/v2/sdk/IOGuide.html?rev=1056369&r1=1056368&r2=1056369&view=diff
==============================================================================
--- trafficserver/site/trunk/docs/v2/sdk/IOGuide.html (original)
+++ trafficserver/site/trunk/docs/v2/sdk/IOGuide.html Fri Jan  7 16:09:06 2011
@@ -58,7 +58,7 @@
 <p>A vconnection read or write operation is different from a normal
         UNIX <code>read(2)</code> or <code>write(2)</code> operation. Specifically, the vconnection operation can specify
         more data to be read or written than exists in the buffer handed to
-        the operation. For example, it's typical to issue a read for <code class="code">INT64_MAX</code> <a class="indexterm" name="id387878"></a>(4 billion) bytes from a network vconnection in order to
+        the operation. For example, it's typical to issue a read for <code class="code">INT64_MAX</code> <a class="indexterm" name="id387878"></a>(9 quintillion) bytes from a network vconnection in order to
         read all the data from the network connection until the end
         of stream is reached. This contrasts with the usual UNIX fashion of issuing repeated
         calls to <code>read(2)</code> until one of the calls finally returns <code>0</code> to indicate the
@@ -76,8 +76,8 @@
 <p>One obvious issue is that the buffer passed to
         <code class="function">INKVConnRead</code> and
         <code class="function">INKVConnWrite</code> won't be large enough - there is no
-        reasonable way to make a buffer that can hold <code class="code">INT64_MAX</code> (4
-        billion) bytes! The secret is that vconnections engage in a protocol
+        reasonable way to make a buffer that can hold <code class="code">INT64_MAX</code> (9
+        quintillion) bytes! The secret is that vconnections engage in a protocol
         whereby they signal to the user (via the continuation passed to
         <code class="function">INKVConnRead</code> and
         <code class="function">INKVConnWrite</code>) that they have emptied  the