This is what threading is good for: connection pooling. Drew Northup, N1XIM
> -----Original Message----- > From: Aaron Stone [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 5:35 PM > To: DBMAIL Developers Mailinglist > Subject: Re: [Dbmail-dev] db_connect before createchild > > > Mikhail Ramendik <[EMAIL PROTECTED]> said: > > > Anton Nekhoroshikh wrote: > > > >> Very much it would be desirable to use OCIConnectionPool for Oracle. > > > > Oracle binding is problematic because of the GPL. And the GPL must be > > there because of the MySQL binding. > > The typical problem is the reverse -- someone with a non-GPL program wants > to use a GPL library. The Oracle license does not apply to us simply by > linking with Oracle, and we are not making an attempt to apply the GPL to > Oracle, and thus not raising a stink with them. So, basically, no problems > here. > > I can think of two ways to solve this connection issue, first, we can see > if MySQL and PostgreSQL would allow us to have a single connection shared > by multiple processes. I have a funny feeling this won't work, though. > > So the second thing I'm thinking is this: db_connect() and > db_preconnect(). For Oracle, all the logic can be in preconnect, which > we'll call before the fork. For everyone else, we'll stub out preconnect > and put the logic into connect. > > Aaron > > -- > >
