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.
>
> ted stockwell
>
> > -----Original Message-----
> > From: Danny Ayers [SMTP:[EMAIL PROTECTED]]
> >
> > Hi,
> >
> > > My conclusion is that ISP's will never allow this. They won't because
> > they have no control whatsoever over the amount of RAM the customer's
> > servlets will ultimately eat up.
> >
> > I can't see many ISPs letting users have such control over their
> > servers. I would have thought they would also have been worried about
> > buggy servlets crashing the server, so rather than leaving it up to the
> > user to add stuff, provide the added service (Guestbook or whatever) in
> > the same manner as any other service.
> >
> > The link to 'Jacob' database looks interesting - now having a look.
> >
> >
>
> ___________________________________________________________________________
> 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

--

Intermittent Web site :
http://members.xoom.com/dayers/_XOOM/dayers/index.html


Alternate email :
[EMAIL PROTECTED]

___________________________________________________________________________
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

Reply via email to