>>> Varalakshmi Allamaraju <[EMAIL PROTECTED]> 23-May-00
12:26:40 PM >>>
Nic wrote:
>> 1. request/response object can be kept if you want (but I can't
see
>> why you would want)
Varalakshmi replied:
>But the spec does indicate otherwise (3.3.3.3).
Sorry! You're quite right about this.
>In the case of context, it's okay. But I don't think this is true
with
>sessions in a distributable setup!
Why not? The distributed part of the implementation should be able to
handle that.
I imagine that most distribution implementations deal with sessions
in much the same way... ie: by having the session itself communicate
changes on it to other servers or have the session notify the session
manager to do it.
Either way there isn't a problem with handing sessions to
sub-threads.
Sessions are implicitly thread-safe because they are open to use by
multiple request/response threads.
>There are implications that one should be aware of. That's what I
was
>trying to communicate.
Apart from the request/response issue I can't see that you're right.
Objects in the servlet environment are just the same as Objects in
any other environment.
Nic
___________________________________________________________________________
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
