Author: buildbot
Date: Mon Apr 15 13:44:08 2013
New Revision: 858546
Log:
Staging update by buildbot for trafficserver
Modified:
websites/staging/trafficserver/trunk/cgi-bin/ (props changed)
websites/staging/trafficserver/trunk/content/ (props changed)
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/transformations.en.html
Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 15 13:44:08 2013
@@ -1 +1 @@
-1465881
+1468064
Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 15 13:44:08 2013
@@ -1 +1 @@
-1465881
+1468064
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.html
Mon Apr 15 13:44:08 2013
@@ -60,7 +60,7 @@
<div id="content">
<p>A <strong>network</strong> <strong>vconnection</strong>
(or<strong> netvconnection</strong>) is a wrapper around a
TCP socket that enables the socket to work within the Traffic Server
vconnection
-framework. See <a href="io-guide#Vconnections">vconnections</a> for more
information
+framework. See <a href="index.en.html#Vconnections">vconnections</a> for more
information
about the Traffic Server abstraction for doing asynchronous IO.</p>
<p>The netvconnection functions are listed below:</p>
<ul>
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/transformations.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/transformations.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/sdk/io-guide/transformations.en.html
Mon Apr 15 13:44:08 2013
@@ -176,19 +176,20 @@ the value of ndone for the input VIO, as
<p>Before sending <code>TS_EVENT_VCONN_WRITE_COMPLETE</code>, your
transformation should
check the number of bytes remaining in the upstream vconnection's write VIO
(input VIO) using the function <code>TSVIONTodoGet</code>
(<code>input_vio</code>). This value should
-go to zero when all of the upstream data is consumed (`TSVIONTodoGet = nbytes
</p>
+go to zero when all of the upstream data is consumed (<code>TSVIONTodoGet =
nbytes - ndone</code>).
+Do not send <code>TS_EVENT_VCONN_WRITE_COMPLETE</code> events if
<code>TSVIONTodoGet</code> is greater
+than zero.</p>
</li>
-<li>ndone<code>). Do not send</code>TS_EVENT_VCONN_WRITE_COMPLETE<code>events
if</code>TSVIONTodoGet<code>is greater than zero.
-The transformation passes data out of itself by using the output vconnection
-retrieved by</code>TSTransformOutputVConnGet<code>. Immediately before Traffic
Server
+<li>The transformation passes data out of itself by using the output
vconnection
+retrieved by <code>TSTransformOutputVConnGet</code>. Immediately before
Traffic Server
initiates the write operation (which inputs data into the transformation),
it sets the output vconnection either to the next transformation in the chain
of transformations or to a special terminating transformation (if it's the
last transformation in the chain). Since the transformation is handed
ownership
of the output vconnection, it must close it at some point in order for it to
-be deallocated.
-All of the transformations in a transformation chain share the transaction's
-mutex. This small restriction (enforced by</code>TSTransformCreate`) removes
many
+be deallocated.</li>
+<li>All of the transformations in a transformation chain share the
transaction's
+mutex. This small restriction (enforced by <code>TSTransformCreate</code>)
removes many
of the locking complications of implementing general vconnections. For
example,
a transformation does not have to grab its write VIO mutex before accessing
its write VIO because it knows it already holds the mutex.</li>