<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br><div><div>On Sep 19, 2008, at 12:19 PM, Luke Graybill wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><br><div class="gmail_quote">On Thu, Sep 18, 2008 at 3:49 PM, Luke Graybill <span dir="ltr"><<a href="mailto:killarny@gmail.com">killarny@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div dir="ltr">My suggested solution is to apply the job-id concept from bgapi to messages as well, and to go a step further; borrow the Asterisk idea of transmitting an identifier along with each command. Every response and event related to that command should then contain the very same identifier in the header.</div> </blockquote></div><br>After speaking with bkw and MikeJ on irc, I'd like to further clarify my suggestion to account for the fact that not all events apply directly to specific commands, but for the ones which do (such as CHANNEL_EXECUTE_COMPLETE, and for non-events, like command/reply) I believe the suggestion stands :)<br> <br>Killarny<br></div> _______________________________________________<br></blockquote>Can you catalog the specific events this would effect?<div>Mike</div><div><br></div></div></div></body></html>