Re: Servlet Zones

[Santhosh Annira]

Here is my view.     1. I have seen it only in Apache JServ.     2. All zones operate under one virtual machine. I think zones just give you a mechanism to create multiple name spaces under one JVM. A servlet zone lets you treat a set of servlet directories as one group and define common characteristics like session time-out, single threaded, etc. ..     3. It does not provide the level of user isolation that a traditional CGI process provides.   Jon Wilmoth wrote: Since my question about how to run a servlet engine (specifically one supporting JSPs) in a cgi-bin environment (without linking to the webserver directly) didn't produce the answers I was hoping for, I turned to researching the options available for installing servlet engines.  I found that the ISP could run multiple servlet zones per engine.  These Zones could would run under a seperate user Id giving the ISP the same security control that CGI processes did.  However, I'm not clear as to the details of Servlet Zones.  Thus, I have the following questions for the many talented & knowledgeable people on this list: 1) Does the Servlet Engine start up a new VM per zone? 2) What happens, in the unlikely event =), when the VM running the servets crashes? 3) Are all other zones in the running in the servlet engine unaffected?4) Does it bring down the entire servlet engine? 5) Are servlet zones part of the Sun spec?  Or just a vendor solution to many an ISP's concerns about security. 6) What are the limitations, if any of Servlet Zones (Memory requirements, hardward req., etc.).  If a servlet zone/seperate JVM is started per entry in the webserver config file, and a JVM process is ~ 2-4 MB it seems there would be a very small number of zones permitted by a ISP simply based on physical constraints. Thanks,Jon