It's not a secret anymore!
The moose likes Servlets and the fly likes SingleThreadModel- when to choose that approach? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Java » Servlets
Bookmark "SingleThreadModel- when to choose that approach?" Watch "SingleThreadModel- when to choose that approach?" New topic

SingleThreadModel- when to choose that approach?

Stefan Elfvinge
Ranch Hand

Joined: Oct 29, 2001
Posts: 52
I know that the SingleThreadModel-interface slows the performance, but isn't that to prefer anyway, for safety, if your application is not speed-dependent or number of users never is more than, say, 20?

arif azim

Joined: Mar 26, 2002
Posts: 7
The SingleThreadModel empty interface is implemented by servlets that does not wish to handle more than one event at a time. It is the servlet engines responsibility to ensure that it only ever invokes one callback method in the servlet at a time.

A server that loads a SingleThreadModel servlet must guarantee, according to the Servlet API documentation, "that no two threads will execute concurrently the service method of that servlet." To accomplish this, each thread uses a free servlet instance from the pool. Thus, any servlet implementing SingleThreadModel can be considered thread safe and isn't required to synchronize access to its instance variables.
For example, a servlet that connects to a database sometimes needs to perform several database commands atomically as part of a single transaction. Normally, this would require the servlet to synchronize around the database commands (lets say, it manage just one request at a time) or to manage a pool of database connections where it can "check out" and "check in" connections (say, it support multiple concurrent requests). By instead implementing SingleThreadModel and having one "connection" instance variable per servlet, a servlet can easily handle concurrent requests by letting its server manage the servlet instance pool (which doubles as a connection pool).
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17033

What's an acceptable performance concession today may not be tomorrow. Don't use single-threading just as a "easy way out"!
On a purely theoretical viewpoint, any need to limit myself to a single-thread approach implies that I wasn't clever enough to get the job done multi-threaded - though I'm sure that sooner or later in the real world, I'll find exceptional cases where single-threading actually BOOSTS performance or some other desirable property.
In the mean time, I limit my use of single-threading to cases where code is either being debugged and I want to eliminate one of the variables in the mix or a system has broken and single-threading gives me a "quick fix" so I can repair it without being under pressure.
Mostly this comes under the rule that it's easier to go from a general solution to a specific one than to back off of one specific solution and move to a different specific solution.

An IDE is no substitute for an Intelligent Developer.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: SingleThreadModel- when to choose that approach?
It's not a secret anymore!