Hi Rob, As far as my experience goes, most of the servlet programmers use multithreaded model. Single threaded model is only useful when you have some shared resource which can not serve more than one requests at a time. Apart from this, even if you have some shared resource, you can always use synchronized functions in order to send a single request to the shared resource. In most of the cases, it solves the problem. Still, I believe, if you have some real critical resource (shared one), you should go for single thread model. best regards, Webduke. -------------------- Programmer/Analyst, St.Louis. --- Rob Jago <[EMAIL PROTECTED]> wrote: > Hello > > I have a question regarding the use of SingleThreadModel , > MultiThreadModel vs managing our homethreads > > Which ones are being mostly used by servlet developers? > > When and why would one be chosen over the other? > > Is there an actual performance issue based on which one you use? > > current environment > > WebSphere 2.0 Advanced, fix pack 1 > NT 4 Server > IIS / IBM HTTP Server > > thank you for any comments you have > > Rob Jago > Programmer Analyst > Ottawa > > ___________________________________________________________________________ > 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 > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___________________________________________________________________________ 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
