[asterisk-dev] Re: FastAGI behaviour in trunk changed recently?

[Tim Ringenbach]

On 7/29/06, Kaloyan Kovachev <kkovachev at varna.net> wrote:
>
> i was trying to narrow the place of the problem. unfortunately i've never
> used
> fast AGI, so i am afraid can't help you much, but if it is necessary to
> close
> STDIN and STDOUT - STDERR also comes to mind.
> i am using local AGI perl scripts and they were working fine with 1.2.3and
> still haven't noticed any problems with trunk.
>
>
Regular AGIs talk over stdin and stdout. You send a new line terminated
command on stdout, receive a response on stdin, and continue in this cycle.
You exit when you want asterisk to continue in the dialplan. If the caller
hangs up, asterisk sends you a SIGHUP.

FastAGIs are slightly different. They talk over a tcp/ip socket instead of
stdin and stdout. If you want asterisk to continue on in the dialplan, you
can close the socket (instead of exiting). Asterisk can neither care or know
what happens to a fastagi's stdin/stdout/stderr, it only knows about the
tcp/ip connection it has to the fastagi.

--Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20060730/4cfe8019/attachment.htm