|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Connection Pooling -- who manages it?At what "level" does connection pooling get managed? For example, if I have
a data access object (DAO) that uses a single connection string to access the database is there a connection pool performance advantage to putting that object in the GAC where it will be shared by all my web applications rather than running it as a private assembly in each individual app? I assume that if it happens in the CLR it won't make any difference. Another example would be if I have different object DAO1 and DAO2 that both use identical connection strings. Do they share a single common connection pool? Again, I would assume that if the CLR is managing it they do share. Thanks. </joel> Joel -
Dispose/Close/Connection Pooling - Here is how it all works !!! http://dotnetjunkies.com/WebLog/sahilmalik/archive/2004/11/12/31798.aspx - Sahil Malik http://dotnetjunkies.com/weblog/sahilmalik Show quote "Joel" <joely***@hotmail.com> wrote in message news:eTjqADu3EHA.3756@TK2MSFTNGP14.phx.gbl... > At what "level" does connection pooling get managed? For example, if I have > a data access object (DAO) that uses a single connection string to access > the database is there a connection pool performance advantage to putting > that object in the GAC where it will be shared by all my web applications > rather than running it as a private assembly in each individual app? I > assume that if it happens in the CLR it won't make any difference. > > Another example would be if I have different object DAO1 and DAO2 that both > use identical connection strings. Do they share a single common connection > pool? Again, I would assume that if the CLR is managing it they do share. > > Thanks. > > </joel> > > > |
|||||||||||||||||||||||