Re: Web enablement options (previously private)

["Nathan M. Andelin" <nandelin@xxxxxxxxxxxxxxxxxxx>]

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