On 10/12/2012 02:16 AM, Olivier wrote: > > > Yes I agree that new features should be committed to new versions but in > this specific case, current 1.8 behaviour is all Queue events but two > (ADDMEMBER and REMOVEMEMBER) are using members name for logging into > queue_log. > > So, to me, queue_log content is currently inconsistent. > > But as I also understand current installs might already have found a way > around (what I rate as a bug), maybe a configuration option would be > acceptable for all. > > What do you think ?
Configuration options such as this are already rampant throughout Asterisk. They make the codebase harder to maintain; they make Asterisk more difficult to configure; they increase the burden on those who attempt to document these options; they make it more difficult to provide correct behaviour in future versions. Making this behaviour configurable implies that future versions of Asterisk will want to maintain the current Queue log behaviour, which is not the case. The only time to have these kinds of configuration parameters is when the behaviour is so onerous that we have to backport the behavioural change, or when the two behaviours should be mutually supported for all future versions. I don't believe either is true in this situation. -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
