See embedded comments below.
Santhosh Annira wrote:
> Here is my view.
>
> 1. I have seen it only in Apache JServ.
>
In fact, the "zone" terminology is specific to 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. ..
All zones *can* run in the same JVM, but this is by no means the only
way to do it. You can in fact run every zone in a separate JVM if you
want, and the JVMs can even be on different servers than Apache runs
on. This is the basis for the user isolation capability, because an ISP
can set up a JVM for each customer, running under their own OS username
(and thus being restricted by those permissions). For more information,
see the Apache JServ documentation related to starting the servlet
engine manually instead of automatically.
You have memory size issues when running large numbers of JVMs on a
server, but these issues can also apply to heavily accessed servers
running CGI-based applications for multiple customers.
>
> 3. It does not provide the level of user isolation that a
> traditional CGI process provides.
>
If you utilize the separate JVM functionality of zones, this statement
is not accurate.
Craig McClanahan
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
