Author: derek Date: Mon Nov 13 23:18:02 2006 New Revision: 197 Modified: sofaswitch/trunk/callflow/docs/current/eachicon.dxy Log: Improve wording slightly. Modified: sofaswitch/trunk/callflow/docs/current/eachicon.dxy ============================================================================== --- sofaswitch/trunk/callflow/docs/current/eachicon.dxy (original) +++ sofaswitch/trunk/callflow/docs/current/eachicon.dxy Mon Nov 13 23:18:02 2006 @@ -174,16 +174,20 @@ while we wait for external events. If processing does fall into here, external events will move graph processing to an Event Collection item as required. Note that if graph processing was such that some events were never registered -for, then execution will be permanently stuck in this item. +for, then execution will be permanently stuck in the "End Graph Processing" +item. +When execution is in the "End Graph Processing" item, waiting for an event to +happen, there is no CPU penalty. + Consider the following graph. \image html faultyendprocessing.png "Permanent stuckly in End Graph Processing" Execution starts at the top, moves to the Event Collection item where it -registers for some event, and then moves to the End Graph Processing +registers for some event, and then moves to the "End Graph Processing" item. Since there is no means of generating events which can be sent to this -call graph, execution will never move to the Event Collection -item. Consequently, this graph will run until it is terminated by user +call graph, execution will never move to the "Event Collection" +item. Consequently, this graph will sit idle, until it is terminated by user intervention.