----- Original Message ----- From: SUBSCRIBE SERVLET-INTEREST Lucy <[EMAIL PROTECTED]> > > I have the Servlet Spec v2.3 Draft 1, and whilst it covers Cookies and Session Cookies, there's only a couple of lines on Threads. [snipped] There is no difference in writing a thread safe code in Servlets as compared to in any other application. The only thing that one needs to understand is that each request is a seperate thread and all these threads may execute concurrently through the service method of a servlet( provided the servlet does not implement the SingleThreadModel). Also one needs to keep in mind that objects such as HttpSession may seem to be local to a thread to a inexperienced programmer but each thread belonging to the same session MAY have the reference to the same HttpSession object. ( The specs do talk about this subtle but important point) > As I said, I loathe session tracking Cookies as a user, so prefer to minimise them as a developer, but not in scenarios where it would be unwise to do so. I'd looking for literature that provides debate on Thread Safety in Servlets rather than just adopting a blanket presumption of Cookie session tracking. And how are these two things related? I fail to understand the link between writing thread safe servlets and the session tracking mechanism used. Can you please elaborate on this? Regds, Gokul > Thanks, Cheers, Lucy >
----------------------------------------------------------------------------------------------------------------------- Information transmitted by this E-MAIL is proprietary to Wipro Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at mailto:[EMAIL PROTECTED] and delete this mail from your records. ------------------------------------------------------------------------------------------------------------------------
