<div>consistency is good.</div>also, make sure that change is clearly explained in the UPGRADE for 10+.<div><br><br><div class="gmail_quote">On Fri, Aug 5, 2011 at 1:13 PM, Terry Wilson <span dir="ltr"><<a href="mailto:twilson@digium.com">twilson@digium.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On Aug 5, 2011, at 8:58 AM, Matthew Jordan wrote:<br>
<br>
> Is it possible to do the following:<br>
><br>
> 1. In the first targeted release, when an Unlink event occurs, also raise the manager_bridge_event. Document that the Unlink event is deprecated and that subscribers should be triggering off the Bridge event.<br>
><br>
> 2. In the second targeted release, remove the offending Unlink events.<br>
><br>
> I'm not sure of the implication of having two events fired for the same action that occurred - that may be worse then simply changing the API. But at least it would give people who are only looking for the Unlink event a chance to switch over between versions.<br>
<br>
</div>This would probably be worse as people who have already worked around the existing inconsistency would be listening for both kinds of events and might then get two events when they expected one.<br>
<div><div></div><div class="h5">--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Clod Patry<br>
</div>