Servlet engines can crash, so if you service all your users in a single
engine and one user does something that crashes the engine then all your
servlet users go down. That's not any better than crashing the web server
itself.
If a single engine is used for each user and the engines start up and shut
down dynamically then you can tolerate an engine crash and conserve the
machine's resources.
ted stockwell
> -----Original Message-----
> From: Danny Ayers [SMTP:[EMAIL PROTECTED]]
>
> Sounds reasonable, assuming the engine is well-behaved. But still, what
> if you have different users with their own servlets? An engine each? I
> suspect ISP sysops would not jump at the chance.
> Cheers,
> Danny.
>
> Ted Stockwell wrote:
> >
> > ISPs would use a servlet engine that runs outside of the web server's
> > process so that if the servlet engine crashes it doesn't bring down the
> web
> > server with it.
> >
>
___________________________________________________________________________
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
