<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>25 okt 2013 kl. 00:50 skrev "Paul Belanger" <<a href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite"><pre style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; white-space: pre-wrap; word-wrap: break-word; ">My only comment is about the naming conventions, we should try and keep AMI events in sync. Right now we have FooBegin / FooEnd, and FooStart / FooStop, and Foo / FooComplete. I'd like us see about pick one format and sticking with it when possible.
I believe Begin / End has been the most recent addition, do we want to default to that?</pre></blockquote></div>I like better the design we decided upon in AMI 1.1 - to have ONE event name and a status field that tells the app if it's start/stop or being/end or something else. We have tried to stop FooBegin/FooEnd and similar constructs for a long time.<div><br></div><div>Like </div><div><br></div><div>Event: foo</div><div>Status: begin</div><div><br></div><div>/O</div></body></html>