tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Jones" <kev...@develop.com>
Subject RE: Tomcat & SingleThreadModel?
Date Fri, 26 May 2000 06:50:45 GMT
SingleThreadModel considered harmful!

SingleThreadModel has so many issues that (IMO) you should never touch it.
It kills scalability (as can be seen by the discussions here) and it DOESN'T
make your servlet thread save. If your servlet uses instance data or
sessions, which is more likely, you still have to worry about
synchronization. Which means that novices get lulled into a false sense of
security and then wonder why they are getting strange errors with their
sessions,

Kevin Jones
DevelopMentor
www.develop.com

> -----Original Message-----
> From: James Cook [mailto:jimcook@iname.com]
> Sent: 25 May 2000 22:22
> To: tomcat-user@jakarta.apache.org
> Subject: Re: Tomcat & SingleThreadModel?
>
>
> ----- Original Message -----
> From: David Eisner <cradle@Glue.umd.edu>
> > Now, what is the relation between the Servlet service() method, and
> > the HttpServlet doGet() method?  Does SingleThreadModel's gaurantee
> > of synchronization on service() imply any such gaurantee for doGet()?
>
> Yes it does. Check out the abstract class javax.servlet.http.HttpServlet.
> This is your servlet's superclass and its service method is
> responsible for
> directing the request to the appropriate doGet, doPost, goTrace, doPut,
> doDelete, or doOptions method.
>
> jim
>
>
> --------------------------------------------------------------------------
> To unsubscribe, email: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commmands, email: tomcat-user-help@jakarta.apache.org


Mime
View raw message