Re: July CCXML Implementation Report: number of connection.merged events - ISSUE-723

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.


>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?

Chris Davis
Interact Incorporated R&D

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