Jon Stevens <[EMAIL PROTECTED]> writes:
> Actually it makes perfect sense that it doesn't.
>
> Hello? Why would it pool connections to itself? The overhead is in creating
> the socket connection and establishing the communication (ie: login and
> authentication), so given that the database is probably on another server,
> what benefit would it be to have the database cache socket connections to
> itself?
>
Hello? Maybe because there may be other resources associated with a
database session than the socket connection itself. Depending on your database
and its implementation the advantage of pooling connections from the client
side might far outgrow the performance improvement you would expect if you
thought the socket connection was all the overhead. Forking or thread
creation being typical areas...
Regards,
Gunnar
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
