W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2007

Re: CCXML "event" attribute in <move> element

From: RJ Auburn <rj@voxeo.com>
Date: Wed, 7 Feb 2007 07:52:26 -0500
Message-Id: <41C9B4A3-951C-4A95-AB5D-E8BC76C528F1@voxeo.com>
Cc: <www-voice@w3.org>
To: Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>


Thanks for your comments on the CCXML LCWD specification. The working  
group will reply to your comments very shortly.



RJ Auburn
CTO, Voxeo Corporation

On Dec 22, 2006, at 11:30 AM, Hrvoje Nezic wrote:

> Dear group,
> I have a question about "event" attribute  in <move> element.
> The specification says about this attribute:
> "The event source from which the event object originated, if any,  
> must be moved to the target session. The event must also be sent to  
> the target session to provide a notification."
> If I understood it well, this event must be a connection or dialog  
> event, like connection.alerting, connection.connected,  
> dialog.started, etc:
> <transition event="connection.connected" name="evt" >
>     <move session_id="target_session_id" event="evt" />
>     ...
> </transition>
> In the above case, the connection.connected event is handled, and  
> it will be sent to another session to be handled again. This seems  
> strange to me. When the above transition starts, the connection  
> object will be in CONNECTED state.
> Before the connection.connected event is being handled in another  
> session, the object will be in wrong state, because according to  
> the specification there is no transition from CONNECTED when  
> current event is connection.connected.
> Another problem is using evt.connection object in the same  
> transition after <move>, while it is concurrently being moved to  
> another session.
> I would like to know if my understanding is correct.
Received on Wednesday, 7 February 2007 12:54:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:39 UTC