> 1. request/response object can be kept if you want (but I can't see
> why you would want)
You mean, keeping these objects outside the context of a request! But
the spec does indicate otherwise (3.3.3.3). Ofcourse, this might work if
the application thread finishes manipulating these objects before the
request thread finishes.
> 2. once a handle to a session has been obtained it is quite legal to
> manipulate it outside of a request
> 3. the servlet context is specifically available for things olike sub
> threads to use
In the case of context, it's okay. But I don't think this is true with
sessions in a distributable setup!
> >Keeping the original intent of servlets in mind- I would not
> implement
> >such things. The rest is a matter of choice.
>
> You may have to... some requirements force you to use a thread.
>
> Just because you haven't come up against the problems don't dismisss
> the solutions.
There are implications that one should be aware of. That's what I was
trying to communicate.
Cheers.
PS: Sorry for the missing subject line in my previous postings.
___________________________________________________________________________
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
