yes, that's my point, if you
don't deprecate the mechanism
in the subject line, then the
servlet context stuff fails to
protect you.
Nic Ferrier <[EMAIL PROTECTED]> wrote:
__________
>>>> Danny Rubis <[EMAIL PROTECTED]> 27-Feb-00 4:07:08 PM >>>
>
>Tim wrote:
>
>>> I think the issue you have missed
>>> is the situation of webhosting ISPs,
>>> there are well understood ways
>>> to support CGI bin applications
>>> from multiple customers on the
>>> same server with minimal
>>> interaction between them, ie only
>>> cpu and bandwidth constraints -
>>> not data.
>>>
>>> In order for servlets to takeoff,
>>> it has to be possible to get this
>>> sort of separation without
>>> running a new JVM per customer.
>
>Danny replied:
>
>>Nicely stated.
>>I develop servlets for a corporate intranet environment, and
>therefore, do not
>>have this problem. But I have also wondered how this problem can be
>solved.
>>Dare we challenge the designers of Java servlets for a solution?
>
>Nic answered (before Craig could /8->)
>
> This is solved by setting up a servlet context for each customer -
>surely?
> (it's what I do)
>
>
>Nic Ferrier
>
>__________________________________________________________________________---
URL http://www.westhawk.co.uk/
___________________________________________________________________________
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
