This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi Ranchers, Due to the inherent threaded nature of servlets, do you still need to implement threads in an app, like, say, in connection pooling, or just let the servlet container do the threading for you? Ex Animo Java! -- Val
"Knowledge is power, but enthusiasm is the key." -- Lavern Barn
I would still do so for long processes, which can be done asynchronously. Things such as long calculations, data insertions that take a long time, etc., can be done in another object, running in its own thread. However, such instances are probably not very common, since most data that is saved needs to be done transactionally, where certain actions are taken when it fails, including flagging the user. The problem with doing this asynchronously, is that the saving will be done in another object and thread, so there would be no way of flagging a failure to the user when the page is returned to the user. Regards, Reuben.