trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1056365 - in /trafficserver/site/trunk/docs/v2/sdk: ConceptIndex.html IOGuide.html
Date Fri, 07 Jan 2011 16:01:30 GMT
Author: igalic
Date: Fri Jan  7 16:01:30 2011
New Revision: 1056365

URL: http://svn.apache.org/viewvc?rev=1056365&view=rev
Log:
s/INT_MAX/INT64_MAX/

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

Modified: trafficserver/site/trunk/docs/v2/sdk/ConceptIndex.html
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/docs/v2/sdk/ConceptIndex.html?rev=1056365&r1=1056364&r2=1056365&view=diff
==============================================================================
--- trafficserver/site/trunk/docs/v2/sdk/ConceptIndex.html (original)
+++ trafficserver/site/trunk/docs/v2/sdk/ConceptIndex.html Fri Jan  7 16:01:30 2011
@@ -75,7 +75,7 @@
 </dt>
 <dt><code>INK_LOG_MODE_ADD_TIMESTAMP</code>, <a href="App_SampleSourceCode.html#Sample_blacklist-1.c"><code>blacklist-1.c</code></a>
 </dt>
-<dt><code>INT_MAX</code>, <a href="IOGuide.html#VconnectionUsersView">The
vconnection user's view</a>
+<dt><code>INT64_MAX</code>, <a href="IOGuide.html#VconnectionUsersView">The
vconnection user's view</a>
 </dt>
 </dl>
 </div>

Modified: trafficserver/site/trunk/docs/v2/sdk/IOGuide.html
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/docs/v2/sdk/IOGuide.html?rev=1056365&r1=1056364&r2=1056365&view=diff
==============================================================================
--- trafficserver/site/trunk/docs/v2/sdk/IOGuide.html (original)
+++ trafficserver/site/trunk/docs/v2/sdk/IOGuide.html Fri Jan  7 16:01:30 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">INT_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>(4 billion) 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,7 +76,7 @@
 <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">INT_MAX</code>
(4
+        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
         whereby they signal to the user (via the continuation passed to
         <code class="function">INKVConnRead</code> and
@@ -163,7 +163,7 @@
                 vconnection is less than the number of bytes the user
                 specifies should be read from the vconnection in a call to
                 <code class="function">INKVConnRead</code>. A common case where
this
-                occurs is when the user specifies that <code class="code">INT_MAX</code>
+                occurs is when the user specifies that <code class="code">INT64_MAX</code>
                 bytes are to be read from a network connection.</td>
 </tr>
 </tbody>



Mime
View raw message