Use of the SingleThreadModel is not considered a good idea. If you think you have to use it, you probably need to rethink your servlet architecture. At one time there was a rumour that SingleThreadModel was going to be deprecated, but it is still in the servlet 2.4 API. Bill
SingleThreadModel has very little in terms of benefits to offer, and thats in built synchronization, which like Smitha said can be achieved thru synchronized calls to the servlets..
However, there's a lot to loose, since servlets implementing this interface leave a large memory footprint and are are not effectively garbage collected. Also, when a servlet requires extra resources like a DB connection, it may open one connection per instance, which is not a good approach.
In essence, this model works nice for smaller applications but not for bigger ones.
-Divij<br />---------------------------------<br />Weinberg's Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.