> Have a single servlet that receives the password and
> user ID for a web site database login?
(If I understand what you are saying...)
Yes, that's the Right Way. Assuming you are storing the database
connection inside the session object, you can redirect a client to the
authentication servlet if the db connection is null. The authenticator
can then read in the login and password as parameters, or can (once
again) redirect the client to a login servlet. If you also use a
push-down stack to keep track of which servlet sent the redirection, the
receiving servlets can then forward the client back to where he started
transparently...
However, this is not a ConnectionPool :-)
--
Within C++ is a smaller, cleaner language
struggling to get out.
It's called Java.
Thomas Moore
[EMAIL PROTECTED] Home Account
Software.Engineer [EMAIL PROTECTED]
phone://732.462.1880:268 NJ Patterns Group Home Page
employer://Celwave, RF http://members.home.net/twmoore/cjpg
___________________________________________________________________________
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
