|
Questions, comments on some CCXML operations: msg#00020web.voice
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 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Request for comments for Media Type registration ofapplication/ccxml+xml: 00020, Al Gilman |
|---|---|
| Next by Date: | amiga amiga emulator amiga rom amiga game amiga game download amiga build doubler scan sync: 00020, burst bum |
| Previous by Thread: | Re: Request for comments for Media Type registration ofapplication/ccxml+xmli: 00020, Al Gilman |
| Next by Thread: | Re: Questions, comments on some CCXML operations: 00020, RJ Auburn |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |