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

Re: CCXML "event" attribute in <move> element - ISSUE-111

From: RJ Auburn <rj@voxeo.com>
Date: Thu, 31 Jan 2008 09:02:24 -0500
To: Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>
Message-Id: <5C3AF203-F8F7-457A-9F62-919BBAFF3C6B@voxeo.com>
Cc: www-voice@w3.org, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>

Hrvoje,

As we have not heard back we are going to assume that our reply below  
is acceptable for you. As such we have closed out this issue in our  
tacker system.

The working group thanks you for your comments and greatly appreciates  
your help in improving the CCXML specification.

Best regards,

	RJ
---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800



On Dec 13, 2007, at 10:17:29, RJ Auburn wrote:

> Hrvoje,
>
> The exact semantics around <move> can indeed be complex, as the issue
> that you raise suggests.  However, the scenario that you described is
> not believed to be inconsistent with the CCXML specification.  The
> 'connnection.connected' event signifies the transition of the  
> associated
> Connection object to the CONNECTED state.  When the Connection is  
> moved
> with this event to a different session, it is not equivalent to a  
> second
> 'connection.connected' event on the same Connection object (thus is  
> not
> equivalent to a CONNECTED --> CONNECTED transition).  Rather, the
> processing of the 'connection.connected' event signifying an ALERTING
> --> CONNECTED transition or a PROGRESSING --> CONNECTED transition is
> just being handled in a different session than the original target for
> the event.
>
> In addition, it is worth noting that the Connection object being moved
> will not be visible to the target session until the <move> occurs;  
> thus,
> even from the perspective of the move target, it does not see the
> Connection object in the already-CONNECTED state until it processes  
> the
> 'connection.connected' event.
> Please let us know if this addresses your question / concern. If you  
> think further clarification is needed please let us know within 3  
> weeks otherwise we will consider this issue resolved.
>
> Best regards,
>
> 	RJ Auburn
>
>
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> Chair, Editor and Chair, CCXML, VBWG, W3C
>
>
>
> On Feb 8, 2007, at 10:39 :02, RJ Auburn wrote:
>
>>
>> This is being tracked as ISSUE-111.
>>
>> 	RJ
>>
>> ---
>> RJ Auburn
>> CTO, Voxeo Corporation
>> tel:+1-407-418-1800
>>
>>
>>
>> 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 Thursday, 31 January 2008 14:03:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 31 January 2008 14:03:20 GMT