It there a rule of thumb for how many connections in the pool you need based on the
total number of user using it?
Tor Kjell
-----Original Message-----
From: Chris Pratt [SMTP:[EMAIL PROTECTED]]
Sent: 25. mars 1999 20:11
To: [EMAIL PROTECTED]
Subject: Re: Connection Pool
Opening a connection to the database is a slow process, first the Java
Runtime must lookup and possibly load and initialize the driver for the
database. Then it must open a communication channel to the database,
probably over some network protocol. Then it must request the connection
from the database and finally it must create the objects to hold the state
information for the connection. Whereas with submitting a statement, all
that JDBC does is submit the statement over the already opened transmission
protocol and wait for an answer. Since Connections are reusable (based on
the user that the connection logged into the database as), there's no reason
to create a new one each time it's necessary to talk to the database. If
you are expecting lots of traffic on your game site, you will have lots of
people logging into your system, but probably not all at the same time. So
if you have a pool of 10 or 50 connections (whatever is appropriate) each
user can log in that much quicker and get on to the fun stuff on your site.
(*Chris*)
----- Original Message -----
From: Alvin Lau <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 25, 1999 10:35 AM
Subject: Re: Connection Pool
> 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
___________________________________________________________________________
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
