The processing of CCXML documents is event driven. The execution of a CCXML document occurs in two phases that correspond to the two parts of the document. The first phase is the execution of the ‘initial' part of the document. This occurs only once.
The second phase is the execution of the ‘event processor' part. In this phase the browser enters an execution loop that receives a CCXML event and uses it to execute the elements within the ‘event processor' part. As an event is received, the section of the document defined for that event is processed. When the processing of the section is complete, the interpreter starts processing the next event on the queue (if one exists) or waits for another event to arrive.
The event processor execution loop continues until certain conditions occur. (see section 9.1, Overview of Event Handling in the CCXML Last Call Working Draft of the Voice Browser Call Control: CCXML Version 1.0 specification, published by W3C and available at http://www.w3.org/TR/ccxml/#event-concepts ). If there is no transition in the document that matches the event, the Blueworx Voice Response CCXML browser provides an event handler. If it is an error event or a kill event, the session exits.