> -----Original Message-----
> From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
> Sent: 11 October 2000 04:45
> To: Ajit Deshpande
> Cc: [EMAIL PROTECTED]
> Subject: Re: Wild Proposal :)
>
>
> Hi Ajit,
>
> It's not entirely clear to me what problem you're trying to
> solve here.
> I'll comment on some of the specifics you've written down here, but I
> may be missing your larger point.
Ajit's examples aren't perfect, but the problem is a real one. The problem
is one of generalisation. Logically, you don't want to put an application
that is 10% web-related into mod_perl. So, you can take it out the other 90%
and stick it into an RPC server, but wouldn't it be nice if there was an
application server framework that handled connections,load balancing and
resource management for you?
> There's DBI::Proxy already. Before jumping on the "we need pooled
> connections" bandwagon, you should read Jeffrey Baker's post on the
> subject here:
>
http://forum.swarthmore.edu/epigone/modperl/breetalwox/38B4DB3F.612476CE@acm
.org
People always manage to miss the point on this one. It's not about saving
the cycles required to open the connection, as they're minimal at worst.
It's about saving the _time_ to open the connection. On a network
application, opening a connection is going to be quite possibly your largest
latency. On a large application doing a lot of transactions per second, the
overhead involved in building connections and tearing them down can lose you
serious time. It also complicates scaling the database server. It's far
better to pay your overhead once and just re-use the connection.
Stephen.
