Resin (http://www.caucho.com)
Are you planning on hosting JSP pages? I've wondered about the security problems of
hosting JSP. If each customer has her own JVM, then things are pretty easy. And thin
servers are getting cheap enough that giving a server per host is becoming reasonable.
Otherwise, how do you prevent them from stepping on each other's toes or even writing
infinite loops? Sure, you can add a security manager. But last time I checked, the
JDK security manager destroys performance.
In contrast, making a JSP/JavaScript sandbox is relatively straightforward with no
real performance penalty.
Scott Ferguson
Caucho Technology
Eric Badger wrote:
> Are there any implementations of JSP that don't require the webserver to be
>restarted every time a change is made to an external bean or class? This is a
>_major_ problem, and I hope it's fixed in Jakarta. I can't imagine hosting JSP pages
>if I have to deal with customers requesting I restart the webserver every 20 minutes
>so they can see their changes.
>
> Eric Badger
> [EMAIL PROTECTED]
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
> For JSP FAQ, http://www.esperanto.org.nz/jsp/jspfaq.html
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
For JSP FAQ, http://www.esperanto.org.nz/jsp/jspfaq.html
