Author: derek Date: Tue Jun 12 22:00:51 2007 New Revision: 315 Modified: sofaswitch/trunk/callflow/docs/callflow.xml sofaswitch/trunk/callflow/docs/chap2.sgml sofaswitch/trunk/callflow/docs/chap3.sgml Log: Text tidyups - get the links to work. Modified: sofaswitch/trunk/callflow/docs/callflow.xml ============================================================================== --- sofaswitch/trunk/callflow/docs/callflow.xml (original) +++ sofaswitch/trunk/callflow/docs/callflow.xml Tue Jun 12 22:00:51 2007 @@ -46,6 +46,7 @@ &chap1; + &chap2; &chap3; @@ -55,12 +56,7 @@ </book> - - > current/faultyjoinexample.png - > current/MakeCall.png - > current/startflow.png - > current/validjoinexample.png - > deathexample.png - > exchildgraph.png +<!-- > exchildgraph.png > exloadnewgraph.png > faultyendprocessing.png +--> \ No newline at end of file Modified: sofaswitch/trunk/callflow/docs/chap2.sgml ============================================================================== --- sofaswitch/trunk/callflow/docs/chap2.sgml (original) +++ sofaswitch/trunk/callflow/docs/chap2.sgml Tue Jun 12 22:00:51 2007 @@ -98,17 +98,16 @@ </tgroup> </informaltable> </figure> - +</para> <para> When Python code generated from the graph in figure -<xref xrefstyle="select: labelnumber"linkend="helloworldexample"/> is run, several messages to and +<xref xrefstyle="select: labelnumber" linkend="helloworldexample"/> is run, several messages to and from the server. First, there is a message to the server saying that a new entity has been created, but without a specific &sofaswitch; identity. The server supplies a specific &sofaswitch; identity. Then, the identity disappears as the generated Python code completes. </para> - </sect1> <sect1> @@ -299,20 +298,24 @@ <para> We have described how &callflow; uses the twisted module (<ulink URL="http://twistedmatrix.com/trac"></ulink>) in Python to handle events. Further, the outcome of this has been stated as -<quote> +</para> +<blockquote><para> processing of events (timers, network packets etc) happens when execution has moved into a "suspend graph processing" control icon. -</quote> +</para></blockquote> +<para> However, this sentence should be extended to note that -<quote> +</para> +<blockquote><para> all control messages which are sent to remote &sofaswitch; entities are sent when execution has moved into a "suspend graph processing" control icon. -</quote> +</para></blockquote> +<para> The following figure <xref xrefstyle="select: labelnumber" linkend="deathexample"/> gives a clear illustration of the order of processing in &callflow; <figure id="deathexample"> -<title>The standard "Hello World" example</title> +<title>An illustration of processing issues</title> <mediaobject><imageobject> <imagedata fileref="diagrams/DeathExample.png" align="center" format="PNG"></imagedata> </imageobject></mediaobject> @@ -323,11 +326,13 @@ message is only sent when execution of control items on this graph is suspended. The third item on this graph causes the id assigned to this graph to be deleted. Thus, on processing the terminate processing control item -(section <xref xrefstyle="select: labelnumber" linkend="TerminateProcessing">), +(section <xref endterm="TermProc" linkend="TerminateProcessing"/>), the message that was queued for sending is never sent. Perusal of the message log on the server will show the creation of a new node (this graph) and the destruction of this node. </para> +</sect1> + </chapter> Modified: sofaswitch/trunk/callflow/docs/chap3.sgml ============================================================================== --- sofaswitch/trunk/callflow/docs/chap3.sgml (original) +++ sofaswitch/trunk/callflow/docs/chap3.sgml Tue Jun 12 22:00:51 2007 @@ -184,6 +184,7 @@ <sect1 id="TerminateProcessing"> <title>Death - terminate processing of this graph</title> +<titleabbrev id="TermProc">Terminate Processing</titleabbrev> <para> Consider the figure <xref xrefstyle="select: labelnumber" linkend="deathicon"/> which shows the icon and graph representation of the control structure used to immediately terminate @@ -703,8 +704,8 @@ go. However, connecting the output of one control item to multiple other control items is incorrect, as the correct direction for execution is not determinable. Thus, the left image in figure -<xref xrefstyle="select: labelnumber" linkend="ambiguousconection"/> is -invalid, but the right image is correct. +<xref xrefstyle="select: labelnumber" linkend="ambiguousconnection"/> is +invalid, but the middle and right images are correct. </para>