Support for threads is only partial functionality of DBI::Pool. Otherwise it should be a ground-up rewrite based on the experiences with Apache::DBI and other wrappers so far. Apache::DBI should become just a thin wrapper on top of DBI::Pool, to handle things like connect_on_init.
The thin wrapper is actually the only part I'm talking about building here. Persistent connections are already available in standard DBI, so I don't need to do anything for that. My goal is just to make something that adds the mod_perl-specific stuff like connect_on_init and a cleanup handler, but doesn't do any of the annoying magical stuff, like automatically making connections persistent (just call connect_cached() for that) or disabling disconnect. The magic stuff could stick around in Apache::DBI for backwards compatibility and for people who want to port CGI scripts with it.
I don't have any time to work on this right now, so it's sort of a moot point. When I do get time for it, I'll post here and we can discuss the design in more detail.
- Perrin
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
