From: Ellen K. 

Well...

I think I was mixed up, partly due to the fact that I've never used .NET
yet.  In fact in my C# book I found advice about closing connections. What
I did find in a pdf I pulled off the web was that ADO.NET associates a
connection pool to each connection string used by any connecting
applications.

Since opening connections is very resource-intensive, I still think there
are many situations where one can just open the connection when the user
logs in and close it when they log out (despite the fact that
"everybody knows" that connection pooling is the way to go).  We
are doing that currently with no problems on two databases that each have
some 600 users and are running on not-fancy servers.

On Sun, 22 May 2005 17:09:11 +0100, "Paul Ranson"
 wrote in message :

>You mean there are connection pooling features in .NET? The problem remains,
>how does the connection pool know that a connection is now free?
>
>And C# does need 'it', that's why a halfway house has been added.
>
>Paul
>
>"Ellen K."  wrote in message
>news:r94t81hcoq5kkuiqjaanl1i7icm28p7f9q{at}4ax.com...
>> C# doesn't need it, connection pooling is automatic.
>>
>> On Fri, 20 May 2005 21:39:18 +0100, "Paul Ranson"

>> wrote in message :
>>
>>>I think you simply don't understand the elementary construct I'm talking
>>>about.
>>>
>>>In C++ I can write code that I can prove closes the connection,
or returns
>>>it to the pool, on every path and in the presence of exceptions. It's
>>>simple
>>>and elegant at the user level. I don't understand why Java and C# don't
>>>have
>>>something similar, it would be compatible with existing syntax.
>>>
>>>Paul
>>>
>

--- BBBS/NT v4.01 Flag-5