<br><div><span class="gmail_quote">On 1/25/06, <b class="gmail_sendername">Sig Lange</b> <<a href="mailto:sig.lange@gmail.com">sig.lange@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span class="q">On 1/25/06, <b class="gmail_sendername">Douglas Garstang</b> <<a href="mailto:dgarstang@oneeighty.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">dgarstang@oneeighty.com</a>> wrote:
</span><div><span class="q"><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Some questions regarding calling Fast AGI from the dial plan.<br><br>Considering that the server side of the Fast AGI has to be able to a) use threading and b) connect to MySQL, this causes some serious limitations. I'm not a C programmer, so development options are either perl or python.
</blockquote></span><div><br>In ref to using perl, You can't connect to the database for each thread? </div></div></blockquote><div><br>you would have to connect to the database from each thread, i strongly suggest you use something like sqlproxy (for mysql) or pgpool for postgres and actually have a thread close the connection once it's done, otherwise you're going to have a very large number of idle connections to the database.
<br></div><br></div>