W3C home > Mailing lists > Public > www-voice@w3.org > July to September 2004

Re: Questions, comments on some CCXML operations

From: RJ Auburn <rj@voxeo.com>
Date: Mon, 20 Sep 2004 07:12:40 -0700
To: Werner Dittmann <Werner.Dittmann@t-online.de>, <www-voice@w3c.org>
Message-ID: <BD743368.1E69B%rj@voxeo.com>

Werner,

Thanks for the comment on CCXML. The CCXML group will discuses these
comments in a upcoming meeting and see what we can do.

Thanks for the feedback,

    RJ


On 09/17/2004 11:56, "Werner Dittmann" <Werner.Dittmann@t-online.de> wrote:

> 
> All,
> 
> the asynchronous operations <createccxml>, <createcall>,
> <dialogprepare>, <dialogstart>, and <createconference> define an ECMA
> lefthand-side expression that will receive the respective id of the
> newly created object. The same id is returned in the associacted
> event, e.g. ccxml.created. What is the rational behind this?
> 
> Because all actions are asynchronous it is not guaranteed that they
> will succeed and having an id before the operation was finished
> successfully, i.e. the opject really created, does not make sense.
> 
> Providing the id only with an event that indicates a success makes it
> easier to implementent a CCXML interpeter because no "look-ahead"
> generation of ids is necessary.
> 
> In addition, it is sometimes appropriate to defer the generation of an
> id until the object is really created and activated by the
> platform. This is the case at least for some call control protocols,
> e.g. SIP, ISUP, etc. where the connectionid identifies the created
> conection.
> 
> Any thoughts?
> 
> Regards,
> Werner
> 
> 
> 

---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800
Received on Monday, 20 September 2004 14:13:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:26 UTC