- From: RJ Auburn <rj@voxeo.com>
- Date: Thu, 26 Mar 2009 11:33:31 -0400
- To: rajeshn@huawei.com
- Cc: www-voice@w3.org, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>
Rajeshn, The working group has reworked the ccxml.exit event text to be a bit more clear. ------------ Old Text ------------ This event is generated when a CCXML document executes an <exit>, having an unhandled "error.*" or ccxml.kill event. This event is only generated when the session executing the <exit/> has a parent session. This event is sent to the parent session and not the session executing the <exit/>. ------------ NEW Text ------------ This event is generated when a CCXML session is terminated for any reason, if the terminated session has a parent session. This event is sent to the parent session and not the session that was terminated. We hope that this has clarified the issue for you. At this point the working group thinks the issues is resolved and closed out the problem in our tracker database. If you still have questions please let us know and we will be happy to further clarify. Best regards, RJ --- RJ Auburn CTO, Voxeo Corporation Chair, Editor and Chair, CCXML, VBWG, W3C On Feb 12, 2009, at 8:25 AM, RJ Auburn wrote: > > Rajeshn, > > This is being tracked as ISSUE-569. > > Thanks, > > RJ > > --- > RJ Auburn > CTO, Voxeo Corporation > tel:+1-407-418-1800 > > On Feb 9, 2009, at 9:03 PM, Rajesh N wrote: > >> Hi, >> >> I have a doubt regarding the ccxml.exit event posted to the parent >> session when the child session ends. >> >> The spec says.. "This event is generated when a CCXML document >> executes an <exit>, having an unhandled "error.*" or ccxml.kill >> event" >> >> From my interpretation of this sentence and the subsequent >> explantion of the "reason" attribute, I find three possibilities >> for child session to terminate: >> >> a) Child session encounters an <exit> element in any transition >> (normal event / error event / kill event) >> b) Child session recieves an(y) error event (error.*), but there is >> no transition to handle it. >> c) Child session recieves a ccxml.kill event. >> >> My doubt is regarding option (c) above. There are 3 sub- >> possibilities for this case: >> >> (i) Child session has a transition to handle to ccxml.kill event >> and the transition also has an <exit> element. Event handling >> results in the processing of <exit>. >> (ii) Child session has a transition to handle to ccxml.kill event, >> BUT the transition DOES NOT have an <exit> element. >> (iii) Child session DOES NOT have a transition for ccxml.kill event >> >> The child session should terminate in all these cases. Should >> ccxml.exit be posted to parent session in all these cases? >> >> The basic reason for this doubt is a small level of ambiguity >> associated with the phrase "having an unhandled "error.*" or >> ccxml.kill event". Does the "unhandled" apply to only error.* or >> both error.* and ccxml.kill? >> >> Please clarify. >> >> Thanks >> Rajesh >> > >
Received on Thursday, 26 March 2009 15:35:38 UTC