From: "Paul Ranson" 

The 'Web app' serves up a page at a time, all the db access is done from
the web server, so the web app needs a connection for each page served. It
should get one from the pool at the start of page processing and return it
at the end. Using a pool means this is very cheap compared to an actual db
query. User authentication should be separate and not attached to a
specific db connection. Or am I missing something?

Paul

"Adam"  wrote in message
news:4291b34e$1{at}w3.nls.net...
> Ellen K. wrote:
>
>> I guess the new system will use connection pooling but what we have now
>> with our SQL Servers is the user's connection is created when s/he first
>> logs in, and persists until s/he logs off.  This is contrary to the
>> Received Wisdom but works great.
>>
>
> Fine & works great in many circumstances (esp low number of users (e.g.
> some system / "DBUser" users)). Not so great if you have a
web app thingy
> with lots of users each of which must be a DBUser given people just close
> their browser & thus the web app has no real way of knowing (http is
> connectionless/stateless) if the connection can be closed/returned to the
> pool
>
> Horses for courses.
>
> Adam

--- BBBS/NT v4.01 Flag-5