Danny Ayers wrote:
> > Gerhard wrote:
> > My conclusion is that ISP's will never allow this...
>
> 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...
Hi,
I don't see why they'd have any problems. These two comments are directly about
servlets. But they don't address (say) Perl CGI programs, which are traditional
security
hazards, use mega-resources, and which all webhosts allow. How are servlets any more
resource-hungry than Perl CGI?
I think, and from what I've seen, once ISP's understand and are comfortable with the
servlet idea, there's no problem with it.
Now, your example was (as far as I understand) of a dbms implemented in Java, which
runs in the user's servlet space. That's pretty wasteful - starting a dbms just for
one
customer. BUT, there's nothing stopping anyone who's read "Perl for Dummies" from
writing a CGI script that sucks up a XXX-megabyte file and processes it for each HTTP
GET. In
fact this "slurping" is a recommended perl style in some texts!
- Robb
___________________________________________________________________________
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
