On Thu, Dec 21, 2006 at 09:57:50AM -0500, Lee Jenkins
wrote:>
> I was playing with aelparse last night and I thought it would be nice if
> the output of the it's operation was a little more structured.
>
> I've written a app that allows me to edit ael/conf files from a windows
> environment and upload them to the asterisk box, commit a reload,
> restart, etc, etc.
>
> This is performed through a socket server running on the asterisk box.
> One of the things I was wanting to do was to be able to transfer an ael
> file to the asterisk box, run aelparse (running aelparse -q -d) and pull
> the output from stdout back over to the windows client for inspection.
>
> As it stands, I can parse through the output, especially looking for
> "ael_yyparse" strings, etc for errors. But I'm assuming that
the output
> could/would changes over time.
>
> If the output is not likely to change that much, it's no problem to
> parse the output as it is, but having maybe a standard dump file (like
> using the -w option) produced would be nice and wouldn't need to change
> very much over time.
>
> XML file would be great, but I'd be game for anything that is
structured
> a bit more and not likely to change.
>
> Any thoughts?
Maybe an optional different file descriptor rather than a dump file?
Would that have been of more use to you?
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir@jabber.org
+972-50-7952406 mailto:tzafrir.cohen@xorcom.com
http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir