jon * wrote:
>
> Huh? that statement makes no sense. How does that apply to connections to a
> database? I vote that it is a really really bad idea to store connections to
> a database in a session object.
>
Jon is right that it does not really matter how you log on while it
comes to connection pooling. To my knowledge, connection pooling has
nothing to do with the username that you use to log in.
--
Kishor Patel
i |money Inc.
"FIND A WAY OR MAKE A WAY"
Voice: 416-368-3920 Ext 5012
Fax: 416-368-5505
Email: [EMAIL PROTECTED]
Website: www.imoney.com
___________________________________________________________________________
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
