BJ - SCJP and SCWCD
We love Java programming. It is contagious, very cool, and lot of fun. - Peter Coad, Java Design
Crazy Bikes created by m-Power
42
Originally posted by Gregor Joseph:
Does a Single Threaded Model help in preventing a Servlet from Handling Multiple requests at a time?
Alco-Haul: We move spirits.
Demented Deliberations of a Dilettante
Originally posted by William Brogden:
Limiting the number of concurrent requests can be handled in Tomcat with configuration parameters (see the link in Ben's post) - presumably other servlet containers have similar methods.
Alco-Haul: We move spirits.
Demented Deliberations of a Dilettante
Retire your iPod and start with HD Android music player Kamerton | Minimal J2EE container is here | Light weight full J2EE stack | and build tool | Co-author of "Windows programming in Turbo Pascal"
Originally posted by Sharad Agarwal:
To run off on a tangent, what is the general consensus on using non-standard container specific features? Does that not lead to vendor tie-in? Or is it that the add-on features are usually valuable enough that it is worth the loss in portability?
Originally posted by Ben Souther:
If this was a setting in web.xml that violated the spec or was 'extra-spec' I'd be dead set against it (Resin has a few of these). In this case, like JVM switches it has more to do with environmental issues and doesn't encourage apps to be written in a non-spec way that would limit their portability.
As Mr. Brogden stated, It's probably a common feature in other containers. I haven't used enough to say.
Alco-Haul: We move spirits.
Demented Deliberations of a Dilettante
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |