|
From: "Joe Pluta" <joepluta@PlutaBrothers.com> > I believe the latest version of the toolbox supports persistent > connections, Nathan. The host server (for database support) has supported persistent connections for as long as I can remember. As far as I know it's controlled entirely by the client, not the server. In my mind, I was comparing it to the design of the HTTP server, which has a configurable pool of lightweight threads that are always active and waiting for the next request. In my opinion, that is the right design for the dynamics of the Internet. From: "Walden H. Leverich" <WaldenL@TechSoftInc.com> > Actually the host servers are prestart jobs, so there is a little less > overhead. The communication job that receives the request is a prestart job. As far as I can tell the job that handles the request is a new job. > The important thing you're missing though is connection pooling > on the OLEDB side. Did you mention it? Or should I have assumed that connection pooling is the default behavior for ASP? Doesn't the script author have to ask for it? Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.