[Asterisk-Users] Fast AGI performance question

[Eric Lyons]

I'm building a fast AGI application (server written in Perl using Net::Server), and have a sort of design performance question.

Is fast AGI keeping the equivalent of a Manager API session open until it returns?  Are there still deadlocking issues there (in 
1.2)?  My assumption is that the fast AGI application -- which handles all incoming calls (_X. in dialplan context) -- should do its 
business (db lookups, setting channel variables, etc) as quickly as possible, then allow control to go back to asterisk in the dial 
plan for max performance.  Certain applications would require staying in the call path for the duration of the call, and presumably 
these would have more difficulty scaling?

Eric.