>So would it make sense to connect to the DB server directly? A Perl or
>PHP class certainly can handle connection pooling.
I don't think that's necessary -- the connection server works well enough
for the version 1 (Perl) back-end, and the version 2 (Java) servlet is
already written -- it will basically *be* the DB server, while the servlet
container/web server does what the connection server does in version 1.