The only reason for me to have any contact with the container is to make resources available to the container.
Jack On Tue, 07 Dec 2004 13:41:06 +0800, Andrew Hill <[EMAIL PROTECTED]> wrote: > <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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
