Questions, comments on some CCXML operations

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

Received on Friday, 17 September 2004 18:55:01 UTC