On Wed, 22 Mar 2006, Daniel Swarbrick wrote:
> One of the great things
> about redesigning the dialplan language is that we won't have to dip
> into AGI for things like accessing an enterprise DB anymore. If we
> choose a mainstream language, it's already going to have support for
> mainstream databases.
While this is a valid point, dont forget that there are many good reasons
for having things like AGI around. just a couple off the top of my head:
A) I have a complex LCR routing engine htat is integrated with a stag of
other functions. If it crashes I dont want to take out the whole system.
Always a possibility (how many of us have seg-faulted apache with bad
perl/php code running mod_{perl|php}
B) with the AGI interface this is a very very clear breakpoint (ie:
STDIN/STDOUT) from what is GPL and what is NOT GPL. (arguments can be made
that there are ways to avoid this with in the GPL on the same box but I
have not found anything short of a socket or pipe that really eliminates
all doubt)
C) I have a call processor that is very intensive and controls a call from
"exten _X.,1... til its dead and do not want it to impact the load on the
call server as its doing something stupid like software transcoding to
G729 and G723.1 so I need to run it as FastAGI on a totally separate box
Niho
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
