>> For connection pooling to work, doesn't the objects that create the connection be
>working in a Com+ environment?
No. The SQL Server .NET Data Provider and OLE DB .NET Provider both provide connection
pooling.
-bc
-----Original Message-----
From: franklin gray [mailto:[EMAIL PROTECTED]]
Sent: Wed 22/05/2002 14:24
To: [EMAIL PROTECTED]
Cc:
Subject: Re: [ADVANCED-DOTNET] Help Architecting A Middle Tier
I have a questions about connection pooling.
For connection pooling to work, doesn't the objects that create the connection
be working in a Com+ environment?
With my current setup, I have Web Services as the backend of my app so that I
can go through firewalls. My web services create objects and execute methods of that
object such as Save or Retrieve. In the methods, I create an object that contains a
sqlConnection and I pass this connection object around to the commands to perform the
process. This is not in a Com+ environment (yet). Do you think this will cause much
more of a strain on the server?
If I have 5 clients that are retrieving some data, I have 5 connections open,
right? Right now the SQL Server is on the same machine as the Web Service, so we
don't have much network traffic dealing with the connections, but we trying to design
it to be scalable so that some users will use different DBs and different Servers when
we get into the hosting phase. I wonder how much of a problem that will be.
You can read messages from the Advanced DOTNET archive, unsubscribe from
Advanced DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
(Ƨ杙,j~&vqC93DM܆+{.n+vqC93DN칻 &-z ++-aجr,uޖ\
