Hi,
On Mon, 24 May 1999, Guillaume ORIOL wrote:
> what do you mean exactly ? Is the use of connection pools just a matter of
> efficiency ?
>
>
Yes, in most cases. Second reason is sparing DB-connection licenses.
In some heavy-load moments you can have more opened sessions
than available
>Alternately do authentication with Connection objects and then
>discard them and use the Connection pool.
>
>But this only gives you login authentication and adds significant
>load to the the db server.
>
>Connection pools aren't always necessary.
>
>Think
>>> Cezar Totth <[EMAIL PROTECTED]> 5/24/99 4:43:19 PM >>>
> Some improvements are possible, to ease security rules
implementation,
> like using one pool (userid/pass) for "reporting" parts of your
app,
> and a pool with a more privileged userId for critical operations
that
> change important data
Hi,
On Mon, 24 May 1999, Guillaume ORIOL wrote:
> In a servlet/web architecture (browser-web server-servlet-database),
> the servlet is the only program which directly accesses the database.
> According to many messages I read in this mailing list,
> the best solution for accessing database
> wi
In a servlet/web architecture (browser-web server-servlet-database),
the servlet is the only program which directly accesses the database.
According to many messages I read in this mailing list,
the best solution for accessing database
within a servlet seems to be connection pooling.
And if I am r
