On Tuesday 06 May 2008 02:16:47 Johansson Olle E wrote: > 5 maj 2008 kl. 19.58 skrev Tilghman Lesher: > > On Monday 05 May 2008 11:24, Johansson Olle E wrote: > >> 5 maj 2008 kl. 17.51 skrev Tilghman Lesher: > >>> On Monday 05 May 2008 09:45, Johansson Olle E wrote: > >>>> Another issue that we need to fix with the MYSQL driver is that > >>>> we're > >>>> lacking a connection pool. Everything seems to be handled over one > >>>> connection to Mysql, which causes issues. > >>> > >>> That's not true. The MYSQL app generally uses multiple connections, > >>> one > >>> for each channel. The only way one might use only a single > >>> connection is > >>> by using a global variable to store a single connection id, but that > >>> method > >>> is not documented anywhere, AFAIK. > >> > >> You talk about the Mysql APP, but is this the case with the Realtime > >> driver as well? > > > > No, the native Realtime driver uses a single connection. The ODBC > > Realtime > > driver generally uses a single connection but can be configured to > > use a > > separate connection for each query. > > So, we're back to where we started. A developer that can help us with > a connection > pool or a separate connection for each query would be a Nice Thing (TM).
What issues are you specifically seeing that merit using multiple connections? -- Tilghman _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
