On Sun, Jun 10, 2007 at 05:29:08AM -0500, Pari Nannapaneni wrote:
> Tim wrote:
> > Wouldn't it be better to split the file up into smaller files each of
> > which can be up/down loaded
> > with the existing mechanism ? All Pari then needs to do is to have a
> > extensions.conf that 'includes' all the little files?
> >
>
> What we have now is working fine, except there are few times where we are
> forced to read
> an entire file on the client side - even if we are looking for just one
> context in it. So i requested
> having an option that can be used to retrieve just the particular context
> from a config file.
>
> The question that was raised is - can we keep adding manager actions
> like these to the web server, because the objective was to have a
> really thin webserver that does not steal any significant
> cpu cycles and to leave all the file parsing to the clients.
The web server indeed should do minimal processing. But this is not the
web server doing work. This is a matter of exposing useful information
available to Asterisk.
There has long been a CLI command 'show dialplan <context>'. So I
suspect that getting just a specific dialplan context is some very
relevant information. And probably the more general request of "get
section foo from onfig file bar".
Ditto for "get me a list of all the section titles from config file
bar".
Does that add much extra processing on the Asterisk server?
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
