p.s. I'm hoping DBI 1.35, which I've just released, will be fairly stable and I can aim to put new things like this, and 'take_imp_data' for Stas, into development releases leading up to a DBI 1.36.
So how do we proceed from here? Should we take something like DBD::myqsl and work out the API on it? And then try some other package?
we also need to spec out how to maintain more than one pool (1 pool per 1 dsn). I was thinking that using some sort of hash list will do (hashing on dsn and then having a linked list on each entry.) As Philippe has pointed out mod_perl 2.0's modperl_tipool.[hc] can be re-used. (tipool = Thread Interpreter Pool)
Finally, there is a bug with threads.pm which we may have problems with under natively threaded apps, like mod_perl:
http://archive.develooper.com/[EMAIL PROTECTED]/msg00649.html
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
