Author: ushachar
Date: Mon Apr 15 13:43:58 2013
New Revision: 1468064
URL: http://svn.apache.org/r1468064
Log:
Fix markdown formatting/typos
Modified:
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.mdtext
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/transformations.en.mdtext
Modified:
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.mdtext
URL:
http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.mdtext?rev=1468064&r1=1468063&r2=1468064&view=diff
==============================================================================
---
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.mdtext
(original)
+++
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/net-vconnections.en.mdtext
Mon Apr 15 13:43:58 2013
@@ -20,7 +20,7 @@ Navigation: [*](*)
A **network** **vconnection** (or** netvconnection**) is a wrapper around a
TCP socket that enables the socket to work within the Traffic Server
vconnection
-framework. See [vconnections](io-guide#Vconnections) for more information
+framework. See [vconnections](index.en.html#Vconnections) for more information
about the Traffic Server abstraction for doing asynchronous IO.
The netvconnection functions are listed below:
Modified:
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/transformations.en.mdtext
URL:
http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/transformations.en.mdtext?rev=1468064&r1=1468063&r2=1468064&view=diff
==============================================================================
---
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/transformations.en.mdtext
(original)
+++
trafficserver/site/trunk/content/docs/trunk/sdk/io-guide/transformations.en.mdtext
Mon Apr 15 13:43:58 2013
@@ -141,10 +141,10 @@ the value of ndone for the input VIO, as
* Before sending `TS_EVENT_VCONN_WRITE_COMPLETE`, your transformation should
check the number of bytes remaining in the upstream vconnection's write VIO
(input VIO) using the function `TSVIONTodoGet` (`input_vio`). This value
should
-go to zero when all of the upstream data is consumed (`TSVIONTodoGet = nbytes
-- ndone`). Do not send `TS_EVENT_VCONN_WRITE_COMPLETE` events if
`TSVIONTodoGet`
-is greater than zero.
-The transformation passes data out of itself by using the output vconnection
+go to zero when all of the upstream data is consumed (`TSVIONTodoGet = nbytes
- ndone`).
+Do not send `TS_EVENT_VCONN_WRITE_COMPLETE` events if `TSVIONTodoGet` is
greater
+than zero.
+* The transformation passes data out of itself by using the output vconnection
retrieved by `TSTransformOutputVConnGet`. 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
@@ -152,7 +152,7 @@ of transformations or to a special termi
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
+* All of the transformations in a transformation chain share the transaction's
mutex. This small restriction (enforced by `TSTransformCreate`) 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
