I wouldn't necessarily do it with a servlet... Create a helper class that
maintains the static pool, then reference the pool through that class from all
of your servlets.
Sam Rose wrote:
> Have a single servlet that receives the password and user ID for a web
> site database login?
>
> This would be initialised first and then many threads created,
> allowing people to login, no?
>
> Other servlets would then be able to call these parameters within a
> session, making the whole process more efficient.
>
> Is this correct or have I lost the plot.
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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
