List:MySQL and .NET« Previous MessageNext Message »
From:James Moore Date:February 3 2005 10:14pm
Subject:RE: Error with connection pooling?
View as plain text  
While I've never looked at the code, my assumption would be that you don't
share open connections.  The model for this sort of thing is usually open/do
work/close, rather than just opening a connection at startup and closing
when you close the app.  Connection pooling means that instead of an "open"
to the database, you get to use a connection that the pool maintains, so the
opens that your application does are very fast (since they're really just
handing you a connection that's already open and in a known state).

Think of "open()" from the application turning into
"getExistingOpenConnectionFromPoolAndAllocateItToMeExclusivelyOhAndIfThereIs
ntAnExistingConnectionPleaseBuildOne()".  Close() is
"ImAllDoneWithThisLetSomeoneElseUseItButYouDontNeedToTellTheDatabaseItsClose
d()."

 - James 


Thread
Error with connection pooling?Bob Dankert3 Feb
  • RE: Error with connection pooling?James Moore3 Feb
    • RE: Error with connection pooling?Joshua Mouch4 Feb
      • Re: Error with connection pooling?Jorge Bastos4 Feb
        • RE: Error with connection pooling?James Moore4 Feb
RE: Error with connection pooling?Bob Dankert4 Feb
RE: Error with connection pooling?Bob Dankert4 Feb
  • RE: Error with connection pooling?ahmet erispaha5 Feb
RE: Error with connection pooling?Bob Dankert5 Feb