[asterisk-dev] Asterisk 1.6 Realtime Database must use ', ' not '|' in appdata field?

Tilghman Lesher tilghman at mail.jeffandtilghman.com
Fri May 30 21:44:10 CDT 2008


On Friday 30 May 2008 20:13:31 Steve Murphy wrote:
> On Thu, 2008-05-29 at 11:58 -0500, Russell Bryant wrote:
> > Steve Totaro wrote:
> > > It sounds like a workable work around (compromise) but still not
> > > optimal in the long run.  If nothing is changed, we will be revisiting
> > > this same thing with a different app or functionality in the near
> > > future.
> > >
> > > I still think that the depreciation route between majore versions is
> > > the best way to go.  Then nothing "breaks" unexpectedly, unless the
> > > User/Admin does not heed the depreciation warnings, therefore it is
> > > their fault.
> > >
> > > I think this should be Asterisk/Digiums's SOP for major functionality
> > > changes for development.
> >
> > I completely agree with you, and it is the policy that we have stuck with
> > pretty well in the past.
> >
> > In this case, I'm slightly torn.  In my _mind_, the pipe as a separator
> > has been deprecated for a long time.  :)  However, I can't find anything
> > that shows that we ever clearly deprecated that.
> >
> > So, in that case, for Asterisk 1.6, I think the default behavior has got
> > to be that the | is still supported.  However, for those that want
> > cleaner and more straight forward parsing, especially with regards to
> > escaping, then an option should be available to disable '|' support, and
> > have ',' as the single supported delimiter.
> >
> > Deprecation warnings should be printed at startup, unless the option is
> > enabled to only support ','.
> >
> > Then, in the future, we can consider completely removing '|' support,
> > after people are given the standard time period to deal with the change.
>
> Remind Murphy to check AEL, and make sure it generates the appropriate
> stuff based on that option...!

I think canonically, the internal delimiter wouldn't change; it's just a
matter of whether we do a translation or not.  That is the way that I've done
it with the compatibility option for pbx_realtime.

-- 
Tilghman



More information about the asterisk-dev mailing list