Try to implement '#include' and '#exec' in a sane way with XML.
You can't just include one valid XML in another. You have to make a
partial XML. And apitting it out is usually way more complicated.
Furthermore, there is the issue of partial processing: do you opt for
one big XML file? Or
On Sun, Dec 09, 2007 at 01:48:58PM -0500, Martin Smith wrote:
Try to implement '#include' and '#exec' in a sane way with XML.
You can't just include one valid XML in another. You have to make a
partial XML. And apitting it out is usually way more complicated.
Furthermore, there is the
What would you be reinventing? Asterisk can already get its
configuration from a MySQL database. You could even add extra fields
in that case to store the phone model and macaddress and integrate
that into your own provisioning tools.
Your application would then retrieve the configuration from
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Using XML for configuration
management,single-source-of-truth, etc.
On Sun, Dec 09, 2007 at 01:48:58PM -0500, Martin Smith wrote:
Try to implement '#include' and '#exec' in a sane way with XML.
You can't just include one valid XML
On Dec 9, 2007 2:05 AM, Philip Prindeville
[EMAIL PROTECTED] wrote:
..snip..
You think that an Asterisk configuration is a lot larger than a Cisco
5850 Access Server or a 7216 core router?
IOS doesn't use XML for configuration. What's a 7216?
--
Kristian Kielhofner
Neat. Does that reference mention anything about how XML was
originally designed as a generic storage mechanism for data being
moved from one architecture to another where the original meaning of
the data might be lost due to differences of those architectures? I
suppose a case can be
Kristian Kielhofner wrote:
On Dec 9, 2007 2:05 AM, Philip Prindeville
[EMAIL PROTECTED] wrote:
..snip..
You think that an Asterisk configuration is a lot larger than a Cisco
5850 Access Server or a 7216 core router?
IOS doesn't use XML for configuration. What's a 7216?
Tilghman Lesher wrote:
On Friday 07 December 2007 20:12:12 Philip Prindeville wrote:
Darryl Dunkin wrote:
You can store most of the configurations in a database which may be
more
accessable to you.
Perl can also parse these configurations quickly enough if you know
how
to use the input
On Saturday 08 December 2007 00:51:44 Philip Prindeville wrote:
Tilghman Lesher wrote:
On Friday 07 December 2007 20:12:12 Philip Prindeville wrote:
Darryl Dunkin wrote:
You can store most of the configurations in a database which may be
more accessable to you.
Perl can also parse
On Sat, 8 Dec 2007 12:22:28 -0600, Tilghman Lesher wrote:
Well, after hand-coding HTML and SGML for 15+ years, XML isn't all that
much of a stretch.
And so can I, but to most people, XML looks like gobbleygook. BTW, 15+ years
for a markup language (HTML) that has only been around for 14
Tilghman Lesher wrote:
And finally, another person has already made the point that most XML
editors are graphical in nature. A great many Asterisk installations
are installed in locations where a graphical front end is not
practical.
ssh -X will deal with that.
/Per Jessen, Zürich
--
On Sat, Dec 08, 2007 at 09:31:28PM +0100, Per Jessen wrote:
Tilghman Lesher wrote:
And finally, another person has already made the point that most XML
editors are graphical in nature. A great many Asterisk installations
are installed in locations where a graphical front end is not
Ryan Burke wrote:
Tilghman Lesher wrote:
On Friday 07 December 2007 20:12:12 Philip Prindeville wrote:
Darryl Dunkin wrote:
You can store most of the configurations in a database which may be
more
accessable to you.
Perl can also parse these configurations quickly
Tilghman Lesher wrote:
On Saturday 08 December 2007 00:51:44 Philip Prindeville wrote:
Tilghman Lesher wrote:
On Friday 07 December 2007 20:12:12 Philip Prindeville wrote:
Darryl Dunkin wrote:
You can store most of the configurations in a database which may be
On Sat, 2007-12-08 at 13:55 -0800, Philip Prindeville wrote:
Going back to my original posting, I was also suggesting that the parse
tree from Asterisk could be read in and then dumped out as XML, so that
other software could then ingest it... using it as a common format for
passing
Jared Smith wrote:
On Sat, 2007-12-08 at 13:55 -0800, Philip Prindeville wrote:
Going back to my original posting, I was also suggesting that the parse
tree from Asterisk could be read in and then dumped out as XML, so that
other software could then ingest it... using it as a common
On Sat, Dec 08, 2007 at 09:43:24PM -0800, Philip Prindeville wrote:
Jared Smith wrote:
On Sat, 2007-12-08 at 13:55 -0800, Philip Prindeville wrote:
Going back to my original posting, I was also suggesting that the parse
tree from Asterisk could be read in and then dumped out as XML,
Tzafrir Cohen wrote:
[snip]
3 of the handset manufacturers that I use, 1 of the firewalls, and 2 of
the video-conference engines all use XML. And the list gets longer
every day.
Most of the programs I have don't use XML. And I only feel better.
Eventually, they will start to
I'm starting work on some provisioning tools to simplify plugging in and
configuring hard SIP handsets and conference bridges (maybe eventually
MPEG-4 PoE video cameras that speak SIP as well).
Issue is that I'd like to glean as much information out of the
configuration files... but don't
On Friday 07 December 2007 20:12:12 Philip Prindeville wrote:
Darryl Dunkin wrote:
You can store most of the configurations in a database which may be more
accessable to you.
Perl can also parse these configurations quickly enough if you know how
to use the input record seperator ($/)
That's sort of my point: that you have to reinvent it, and it's easy to
get wrong.
Darryl Dunkin wrote:
You can store most of the configurations in a database which may be more
accessable to you.
Perl can also parse these configurations quickly enough if you know how
to use the input
Tilghman Lesher wrote:
On Friday 07 December 2007 20:12:12 Philip Prindeville wrote:
Darryl Dunkin wrote:
You can store most of the configurations in a database which may be more
accessable to you.
Perl can also parse these configurations quickly enough if you know how
to use the
-Commercial Discussion
Subject: [asterisk-users] Using XML for configuration
management,single-source-of-truth, etc.
I'm starting work on some provisioning tools to simplify plugging in and
configuring hard SIP handsets and conference bridges (maybe eventually
MPEG-4 PoE video cameras that speak SIP
23 matches
Mail list logo
