[asterisk-dev] Asterisk 1.6 Realtime Database must use ', ' not '|'
Jay R. Ashworth
jra at baylink.com
Fri May 23 13:26:48 CDT 2008
On Fri, May 23, 2008 at 09:03:19PM +0300, Tzafrir Cohen wrote:
> On Fri, May 23, 2008 at 08:38:10AM -0400, Ward Mundy wrote:
> > This is another example of how something that may appear to developers to be
> > trivial has enormous negative consequences to those actually using Asterisk
> > to do 'real work.' This one change breaks dialplan code for every AGI
> > function call. For organizations with elaborate custom dialplans, this is
> > expensive to fix particularly if some outside company (that's no longer
> > around) wrote their dialplans. What is so difficult about supporting BOTH
> > the comma and vertical bar as delimiters? The argument always has been that
> > some of these changes were necessary to improve the performance of Asterisk.
> > Not sure that holds water this time around.
>
> So let's clarify what was the situation in 1.4 and what has changed in
> 1.6 .
>
> <Up until 1.4>
>
> Many of us are used to writing in extensions.conf:
>
> exten => 123456,1,AppFooBar(arg1,arg2,arg3)
>
> But when you look at the result: 'dialplan show context-foo-bar' it
> would look like:
>
> '123456' => 1. AppFooBar(arg1|arg2|arg3)
>
> Thus when processing the dialplan from extensions.conf, asterisk would
> silently translate commas to pipes.
So... Tilghman's large crowd of applauders... won't be affected at all,
since they're already using commas, and those will keep working.
Got it.
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com '87 e24
St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
Those who cast the vote decide nothing.
Those who count the vote decide everything.
-- (Joseph Stalin)
More information about the asterisk-dev
mailing list