Re: July CCXML Implementation Report: number of connection.merged events - ISSUE-723 from Chris Davis on 2010-08-20 (www-voice@w3.org from July to September 2010)

From: Chris Davis <davisc@iivip.com>
Date: Fri, 20 Aug 2010 09:21:26 -0500
To: www-voice@w3.org
Message-ID: <4C6E8F66.2010709@iivip.com>

It seems logical to me to issue one event per connection to indicate
that each connection had transitioned to DISCONNECT as a result of the <merge>.

This seems consistent with other parts of the CCXML Recommendation that require
a connection.* event to trace each state change of each connection.

Regards,
Chris

>Paolo,
>
>This resolution is acceptable for us although we would prefer to change 
>the Specification to generate only one 'connection.merged'.
>
>Could you please explain us what is the rationale for having two 
>'connection.merged' events?
>
>Thanks,
>Petr


-- 
Chris Davis
Interact Incorporated R&D
512-502-9969x117

Received on Friday, 20 August 2010 14:22:05 UTC