Author: derek Date: Wed Jun 13 18:54:11 2007 New Revision: 323 Modified: sofaswitch/trunk/callflow/docs/chap2.sgml sofaswitch/trunk/callflow/docs/chap3.sgml Log: Keep tidying the docs and add more links. Modified: sofaswitch/trunk/callflow/docs/chap2.sgml ============================================================================== --- sofaswitch/trunk/callflow/docs/chap2.sgml (original) +++ sofaswitch/trunk/callflow/docs/chap2.sgml Wed Jun 13 18:54:11 2007 @@ -57,6 +57,15 @@ </para> <para> +When Python code generated from the graph in figure +<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> + +<para> The output connection of a control element should be connected to the input connection of one other control element. Joining the output connector of a control element to two other places is ambiguous, and is an error. Thus, the @@ -100,14 +109,7 @@ </figure> </para> -<para> -When Python code generated from the graph in figure -<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> @@ -134,9 +136,9 @@ </para> <para> While processing each of the nodes in the supplied graph, it is -ignoring all timer events. Execution continues until it falls of the end of -the graph, or passes through an Eventer type structure and goes nowhere. Once -execution has gone nowhere, the system will process pending events. +ignoring all timer events. Execution continues until it is suspended +(section <xref endterm="SuspendProcessing" linkend="SuspendProcessingSec"/>). +Once execution has been suspended, the system will process pending events. </para> Modified: sofaswitch/trunk/callflow/docs/chap3.sgml ============================================================================== --- sofaswitch/trunk/callflow/docs/chap3.sgml (original) +++ sofaswitch/trunk/callflow/docs/chap3.sgml Wed Jun 13 18:54:11 2007 @@ -659,7 +659,7 @@ describing the identity of this graph (so noone else can communicate with this graph). Further, this graph has not requested any node, so there will be no incoming messages about created &sofaswitch; entities. This graph has not -registered with any &sofaswitch; entity as the master node (section (xref +registered with any &sofaswitch; entity as the master node (section <xref endterm="MasterNode" linkend="MasterNodeSec"/>) so another source of events to this graph is blocked. Thus, this graph will sit forever in the suspend processing control item and do nothing. @@ -1821,7 +1821,8 @@ <sect1> -<title>Suspend graph processing</title> +<title id="SuspendProcessingSec">Suspend graph processing</title> +<titleabbrev id="SuspendProcessing">Suspend processing</titleabbrev> <para> Consider the figure <xref xrefstyle="select: labelnumber" linkend="suspendprocessingicon"/> which shows the icon and graph representation of the control structure used to suspend the