<snip>
I would never, of course, dream of grabbing a request object, or
similar things, and holding it in a new thread. I would never, ever,
anytime dream of doing that. Yuk!
</snip>
hehe.
What about the ServletContext object though?
Dakota Jack wrote:
> Spawning threads is something I do almost as a matter of course in my
> programming. I don't know what I would do without doing that.
>
> I would never, of course, dream of grabbing a request object, or
> similar things, and holding it in a new thread. I would never, ever,
> anytime dream of doing that. Yuk!
>
> As those who have noted my submissions to this list will know, I am
> big on state management outside the request, page, session and
> application scopes and this seems to almost necessarily involve
> threads in the solutions my head devises. I also make extensive use
> of Doug Lea's work which is essentially multi-threading.
>
> Like everything else, you can code threads well and badly. I guess
> the upshot of bad coding with threads is particularly serious, so you
> don't want newcomers being assigned these tasks?
>
> Jack
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
|