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 calls to same web service. Some research showed me
that the best practice is to open and close connection.
Thanks for the response
Cheers
Seref
Ryan Heath wrote:
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 means a new
initialization, and for clients continuously using the web services,
server side use of connection pooling is not possible.
Are you sure you are using connection pooling?
Granted, the very first request may initialize some resources, but
*all* subsequent requests should benefit from this, and should not
init any resource on behalf of connection pooling.
Web services being stateless has nothing to do with not being able to
use connection pooling, or maybe I did not understand what you are
saying...
// Ryan
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
