trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zw...@apache.org
Subject [12/18] git commit: Fix block indentation, and bullets describing continuation data caveats.
Date Sat, 08 Mar 2014 14:46:24 GMT
Fix block indentation, and bullets describing continuation data caveats.


Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/bc10a6e7
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/bc10a6e7
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/bc10a6e7

Branch: refs/heads/master
Commit: bc10a6e7206049d188eb316ec7a51afd0eb8d080
Parents: ce6cb8d
Author: Leif Hedstrom <zwoop@apache.org>
Authored: Sat Mar 8 00:28:20 2014 +0000
Committer: Leif Hedstrom <zwoop@apache.org>
Committed: Sat Mar 8 07:45:49 2014 -0700

----------------------------------------------------------------------
 doc/sdk/continuations.en.rst | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafficserver/blob/bc10a6e7/doc/sdk/continuations.en.rst
----------------------------------------------------------------------
diff --git a/doc/sdk/continuations.en.rst b/doc/sdk/continuations.en.rst
index 1981fd7..34e3a04 100644
--- a/doc/sdk/continuations.en.rst
+++ b/doc/sdk/continuations.en.rst
@@ -73,20 +73,18 @@ Caveats that could cause issues include the following:
 
 -  a continuation has data associated with it (``TSContDataGet``).
 
-| \*
-| the reentrant call passes itself as a continuation to the reentrant
-API. In this case, the continuation should not try to access its data
-after calling the reentrant API. The reason for this is that data may be
-modified by the section of code in the continuation's handler that
-handles the event sent by the API. It is recommended that you always
-return after a reentrant call to avoid accessing something that has been
-deallocated.
+-  the reentrant call passes itself as a continuation to the reentrant
+   API. In this case, the continuation should not try to access its data
+   after calling the reentrant API. The reason for this is that data may be
+   modified by the section of code in the continuation's handler that
+   handles the event sent by the API. It is recommended that you always
+   return after a reentrant call to avoid accessing something that has been
+   deallocated.
 
 Below is an example, followed by an explanation.
 
 ::
 
-        ::::c
     continuation_handler (TSCont contp, TSEvent event, void *edata) {
         switch (event) {
             case event1:


Mime
View raw message