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 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. Would it be possible to open and share an application level set of connections to various sql servers? I guess thread safety for ADO.NET connections would be an issue here. Conn. pooling is fine, when you're running open and close operations on a conn instance, but for simultaneous requests to web services, a more scalable approach is necessary. Should I look for an answer in .NET enterprise services (the old COM+)? Any pointers would be appreciated a lot
Best Regards Seref Arikan =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
