> 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
- Re: Further on Session problems with Java Servlet P... jon *
- Re: Further on Session problems with Java Serv... Kevin Jones
- Re: Further on Session problems with Java ... Thor Heinrichs-Wolpert
- Re: Further on Session problems with Java Serv... Rod McChesney
- Re: Further on Session problems with Java Serv... Kishor Patel
- Re: Further on Session problems with Java ... Thor Heinrichs-Wolpert
- Re: Further on Session problems with Java Serv... jon *
- Re: Further on Session problems with Java ... Rogatkin, Dmitry M
- Re: Further on Session problems with Java ... Thor Heinrichs-Wolpert
- Re: Further on Session problems with Java Serv... Bob Withers
- Re: Further on Session problems with Java ... Matthew G. Kelley
- Re: Further on Session problems with J... Andres Aguiar
- Re: Further on Session problems wi... Craig McClanahan
- Re: Further on Session proble... Thor Heinrichs-Wolpert
- Re: Further on Session problems wi... Thor Heinrichs-Wolpert
- Re: Further on Session problems with Java ... Thor Heinrichs-Wolpert
- Re: Further on Session problems with Java Serv... John Burns
