It's not a secret anymore!
The moose likes Servlets and the fly likes SingleThreadModel Interface Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "SingleThreadModel Interface" Watch "SingleThreadModel Interface" New topic

SingleThreadModel Interface

Pandurangan Rakesh

Joined: Jun 06, 2004
Posts: 24

I know that servlet is multithreaded by default.By using singlethreadmodel interface does its multithreading capabilities are restricted?to what extent?
also can anyone tell me when we use singlethread model interface?i heard that this is to be deprecated soon?

William Brogden
Author and all-around good cowpoke

Joined: Mar 22, 2000
Posts: 13037
If your servlet implements SingleThreadModel, the servlet engine will ensure that a given instance only handles one request at a time.
In my opinion, SingleThreadModel was created early in the development of the servlet API as a crutch for people having a hard time making the transistion from desktop single user applications to servlets. I know of no valid excuse for using it these days.

Peter den Haan
Ranch Hand

Joined: Apr 20, 2000
Posts: 3252
It has been deprecated in the Servlet 2.4 spec (part of J2EE 1.4) without replacement. Which begs the question: if it was a superfluous, bad idea for servlets, what makes it a good idea for stateless EJBs?

- Peter
I agree. Here's the link:
subject: SingleThreadModel Interface
It's not a secret anymore!