Di
Sounds like a job for connection pooling. I made my own connection pooling
classes, but there are a number of frameworks out there that can be
customized. I think you'll find as you scale up the application to more than
a couple of users that things start to go wrong with just a single
connection.
Mike Nash
JavaCorporate Ltd: Java Components for the Corporate Intranet
http://www.javacorporate.com
-----Original Message-----
From: Sen-sei [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 08, 1999 10:48 AM
To: [EMAIL PROTECTED]
Subject: DB Design question (2 part)
Hi All:
I have a three tier application and the servlet acts as the middle tier
between the user and the database. All of servlets extends database methods
from the class that provides database services (open, close...) The first
called servlet open the conecttion with the DB, and the classes called from
the first one, take profit of this, because is the same connection for all
that extends this class. With this configuration, if two user are at the
same time using the program,
the first user close when finish, the connection to the second user.
I have solved the problem with two or more users, because now the connection
is not closed while there are almost one user using it. (user++ with
Open_DB, and user-- with Close_DB). But now the problem is that i have only
one connection, and I think that the system is going slowly that with one
connection for each user.
Any suggestion??
Di
___________________________________________________________________________
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
