Howdy, Other people have already explained how tomcat does things. I just wanted to chime in saying SingleThreadModel is potentially worse than just a waste of time: it can mislead you into thinking your servlet and all the code it touches is automatically thread safe. It's not.
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Colquhoun, Adrian [mailto:[EMAIL PROTECTED]] >Sent: Thursday, January 23, 2003 6:00 AM >To: 'Tomcat Users List' >Subject: Using SingleThreadModel under tomcat > > > >Hi > >I have a stateless servlet application in which I am considering >implementing SingleThreadModel. I note from the archives a number of posts >which suggest that implementing SingleThreadModel will impose a performance >overhead when running under tomcat. Could anyone provide me with a >explanation of how this performance impact comes about and (in relative >terms) the magnitude of this impact versus the potential impact of using >synchronisation blocks to ensure thread safe code ? > >Thanks > >Adrian > > >======================================================================= >Information in this email and any attachments are confidential, and may >not be copied or used by anyone other than the addressee, nor disclosed >to any third party without our permission. There is no intention to >create any legally binding contract or other commitment through the use >of this email. > >Experian Limited (registration number 653331). >Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF > >-- >To unsubscribe, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
