"Dr. Dragomir D. Dimitrijevic" wrote:
> Hi All,
>
> How grouping servlets in servlet zones in
> Apache/Jserv affect performance? Is there
> any deeper meaning of zones except grouping
> of servlets based on their functionality?
>
There are at least two areas where zones have a purpose beyond organizational
convenience:
* Information Sharing -- although Apache JServ
somewhat predated the concept of "web
application" that is very clear in the 2.2 API,
you should put servlets that need to share
information in the same zone (i.e. the same
servlet context in the terms of later servlet APIs).
* Distributed Processing -- individual zones need
not run in the same JVM, or on the same server.
>
> For example, is there any difference in
> performance between 3 servlets in 1 zone and
> 3 servlets in 3 zones?
>
If all three zones are in the same JVM, little or no difference.
If your web server is overloaded, and the three zones are distributed across
servers of their own, the three zone case could have substantially better
performance. It's very application dependent, though.
Apache JServ in particular lets you play one more game -- you can have more
than one JVM containing the same servlets, and it will do a basic form of load
balancing for you.
>
> Any comment will be greatly appreciated
>
> Dragomir
>
Craig McClanahan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
