[asterisk-dev] Introducing the new ConfBridge

Watkins, Bradley Bradley.Watkins at compuware.com
Wed Feb 23 17:43:47 CST 2011

>-----Original Message-----
>From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-
>bounces at lists.digium.com] On Behalf Of Russell Bryant
>Sent: Wednesday, February 23, 2011 6:27 PM
>To: Asterisk Developers Mailing List
>Subject: Re: [asterisk-dev] Introducing the new ConfBridge
>I kind of like it the other way around.  The reason is that the most natural
>thing to me is have the key in the key/value unique when possible.  By
>having the key sequence as the key, it does that.  If you swap it, you could
>have 20 instances of dialplan_exec = something, which I don't like as much.
>Admittedly, there are plenty of examples of configuration sections in
>Asterisk where a particular key may be duplicated.  For example allow,
>disallow, permit, deny, etc.
>It's a big toss up to me.  I guess I don't care either way.  Speak up if you care
>enough to vote one way or the other, I guess.  If enough people want it
>changed, that works for me.
>Russell Bryant
>Digium, Inc.   |   Engineering Manager, Open Source Software
>445 Jan Davis Drive NW    -     Huntsville, AL 35806  -  USA
>www.digium.com  -=-  www.asterisk.org -=- blogs.asterisk.org

I very much prefer having the key sequence first, action after, as in the original proposal.  I think it helps to visualize the menu a lot better.

- Brad

More information about the asterisk-dev mailing list