"a bunch of singleton pool objects"??? It looks funny. Nice joke, thanks so
much. Actually, using SessionContext for keeping database connections is a
good idea, and you can also, if you want, put singleton pool object to the
session.
Dmitry.
----- Original Message -----
From: jon * <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 10, 1999 3:37 PM
Subject: Re: Further on Session problems with Java Servlet Programming
Book...
> > Actually, it makes lots of sense. If you are using a database's own
> > security setup, allowing and denying table access by roles or users,
> > then connection pools won't work. You need a separate connection for
> > each user.
>
> Ahhh...I fully understand now. Thanks for the clarification.
>
> So, one solution might be to create a bunch of singleton pool objects (ie:
> one for each user) and just use those. Maybe also have a master that
> controls the pools of the singleton objects as well.
>
> -jon
>
>
___________________________________________________________________________
> 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
