It is proposed that the <success/>
element, indicating that a component completed successfully, be replaced by a set of more descriptively named elements, such as <initial-timeout/>
, <end-of-file/>
, etc. These allow the client to correlate the actual completion reason with what are potentially a large set of possible triggers from the original command. For example, setting both max-time and interrupt-on on an Output results in an ambiguous <success/>
reason. In the case of Input, <success/>
will be renamed <match/>
.
Further, it is concerning that node ordering is still being relied upon for disambiguating children of <complete/>
. Currently, the Record component may submit a complete event like this:
<presence to='[email protected]/1' from='[email protected]/fgh4590'>
<complete xmlns='urn:xmpp:rayo:ext:1'>
<success xmlns='urn:xmpp:rayo:record:complete:1'/>
<recording xmlns='urn:xmpp:rayo:record:complete:1'
uri="file:/tmp/rayo7451601434771683422.mp3"