Do you create a new connection each time a user tries to login? Or do you use
the same one each time? The first is extremely inefficient, and the second one
will not allow multiple simultaneous connections, and this is also extremely
inefficient.
It is not just for transactions, it is for maintaining open database
connections that can be used as needed by one or more servlets (or helper
classes).
Alvin Lau wrote:
> I'm building a marketing's games, and I made a login's servlet a few weeks
> ago. What I did is that, when a user login in, first I check the user pw
> and id, and if I find a record in my db, then I create a new user's obj
> and put it in the session.
>
> I really don't understand why you need a connection pool. For me you need
> a connection pool only if you have to do transaction. Am i correct?
>
> If you want to see my codes, just let me know.. :-)
>
> alvin lau
>
> ___________________________________________________________________________
> 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
