Hi
I think there must be a controller object which recieves all the requests for
insertion, updation or delition and forward these requests to an object of DB
class. Controller class must have a single instance of DB class and all the
operations must be implemented in the DB class as member methods.
Shahzad
Kiran Chaugule <[EMAIL PROTECTED]> on 09/08/2000 05:35:56 PM
Please respond to "A mailing list for discussion about Sun Microsystem's Java
Servlet API Technology." <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Shahzad Mahmood/CresSoft)
Subject: Thread safe methods.
Hello Everybody,
I am designing an application where there are a lot of database
operations, viz. query, insert, update, delete. I have a design problem.
I have created a DB class which has a method which does all the
insert update and delete operations. Whenever I want to insert, update
or delete a record, should I create a new instance of my DB class and
call it's method, OR create one instance of DB class per table OR make
my method in the DB class static. What are the design issues to be
considered?
A lot of people have access to the same screens. How do I make sure
that the user is viewing the latest data at any stage?
Thanking u in advance,
Kiran
___________________________________________________________________________
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
