This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Servlets are great, because one instance services an innumerable amount of clients. However, I was wondering (and am too lazy to read the spec).
When a single Servlet class is parameterized in the web.xml file, to create say three different servlet definitions, at runtime, will one instance be created, but run with the appropriate parameterization to make it seem like there are three instances, or is there a definite one to one relationship between servlet definitions in the web.xml file, and instances running.
Remember, I'm talking about the same Java class file, just parameterized differently three times in the deployment descriptor.
SRV.2.2 Number of Instances The servlet declaration which is part of the deployment descriptor of theWeb application containing the servlet, as described in Chapter SRV.13, �Deployment Descriptor�, controls how the servlet container provides instances of the servlet. For a servlet not hosted in a distributed environment (the default), the servlet container must use only one instance per servlet declaration. However, for a servlet implementing the SingleThreadModel interface, the servlet container may instantiate multiple instances to handle a heavy request load and serialize requests to a particular instance.
[ December 28, 2006: Message edited by: Ben Souther ]