>>> 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..
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 about using them before coding, the lack of authenticated
security is a significant issue in some applications.
Nic Ferrier
Tapsell-Ferrier Ltd
www.tapsellferrier.co.uk
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
