half Of Seref Arikan
Sent: Saturday, November 17, 2007 6:44 AM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Sharing an connection pool in ASP.NET
Hi,
I am trying to refactor an Net 2.0 app for better scalibility. The
application uses web services to return data, and the
Hi Ryan,
You are correct, the stateless nature of web services does not matter,
for connection pooling is done at the application domain level, which
covers all web services exposed from an asp.net application.
Not knowing this, I thought that the connection pooling was not
available to various ca
On Nov 17, 2007 12:44 PM, Seref Arikan
<[EMAIL PROTECTED]> wrote:
> The problem is, the first call
> to connection object"s open method takes quite a bit of a resource,
> since this is the first initialization of the connection and also the pool.
> Since the web services are stateless, each call me
mber 17, 2007 6:44 AM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Sharing an connection pool in ASP.NET
Hi,
I am trying to refactor an Net 2.0 app for better scalibility. The
application uses web services to return data, and the code behind the
web services open a connect
Hi,
I am trying to refactor an Net 2.0 app for better scalibility. The
application uses web services to return data, and the code behind the
web services open a connection to a remote sql db, get the data and
close. So far it is a classical use case. The problem is, the first call
to connection ob
