This week's book giveaway is in the Performance forum. We're giving away four copies of The Java Performance Companion and have Charlie Hunt, Monica Beckwith, Poonam Parhar, & Bengt Rutisson on-line! See this thread for details.
Hi, I am trying to update a database using servlets. Servlets must be allowed concurrent users to read and update the database. I have a few design choices in my mind but I am not sure which one is the best in performance and does not cause thread problems like deadlock and so on? Can someone give me a suggestion? Database class- the class that control the connection to the database Threads-used to read, delete and update the database Servlets-response to the users. When user enter into the selected servlets, the servlet will create threads to enter into the database class to read or update the information. Thread will create a new database class and updated the database.Thread is killed when the database is updated. Should the connection to the database be static or non static if i want to ensure that every user who access the website get the most up-to-date information? When does the database get updated(Committed), is it when the database connection is closed or when the statement is closed(the sql query)?