Mike Marchywka wrote:
>
> Although I'm not really sure what impact Thread.stop() could
> have in a servlet engine.
>
No impact at all, because it's deprecated and you
shouldn't be using it anymore. Try this:
http://java.sun.com/products/jdk/1.2/docs/guide/misc/threadPrimitiveDeprecation.html
Writing correct multithreaded code is hard. Writing
correct multithreaded code that is cancellable is
harder. Writing correct multithreaded code that is
cancellable and works within a servlet container is
even harder (and sometimes impossible)
Let's put it this way: Can you explain, clearly and
concisely, why Thread.stop() has been deprecated?
If you can, can you honestly expect that everyone who
will maintain the code you write has an equally good
understanding of the issues?
Writing a servlet that's expected to be up and running
for months at a time is hard enough without adding
intractable thread management problems to the list
of requirements.
Just say no to servlet-spawned threads :-)
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
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
