jd.... but..... but.... Asterisk still fires up a process each time you make an AGI call in the dialplan. You could still have 120 of these lightweight processes running, in _addition_ to the other process. Doesn't sound like it provides much benefit.
-----Original Message----- From: John Daragon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 11, 2006 2:14 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Nested MySQL Commands Douglas Garstang wrote: > Peter, I assume you mean something like this in extensions.conf: > > exten => _X.,1,AGI(master-dial-logic.pl) > > and then there's only one call. All logic would be performed by > the perl script. This has many advantages. One disadvantage however > is that potentially, there could be 120 simultaneous instances of > this script running (one per call). Yes, but if you need it to scale efficiently, each of these could be a very lightweight process. If you used each of these to communicate via RPC or shared memory to a process with a small and configurable pool of database connections (which isn't that difficult), you can build a simple and scalable solution. jd -- John Daragon [EMAIL PROTECTED] argv[0] limited (Asterisk implementation & consultancy) Lambs Lawn Cottage, Staple Fitzpaine, Taunton, TA3 5SL, UK v +44 (0) 1460 234068 f +44 (0) 1460 234069 m +44 (0) 7836 576127 _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
