I have a couple of applications which use a background thread in the servlet
to perform some periodic task. In my case it is quite helpful to use
servlets in this manner because our production web servers are locked up in
a server farm. Using a servlet to control the tasks gives me the ability to
create web-based admin pages for those tasks.
----- Original Message -----
From: Randy Belknap <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 15, 1999 2:52 PM
Subject: Re: stop a servlet thread
> > However, I'm still of the opinion that in general servlets are not the
best
> > solution to performing a periodic self-initiated task
> >
> WebLogic used to (still does?) says you should not create any threads in
> your classes because it kills performance. This would be another
> argument against using a servlet for cron type processing. Instead they
> provide interfaces for building classes that are triggered periodically.
>
>
___________________________________________________________________________
> 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
>
___________________________________________________________________________
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
