Why not move away from the threads approach altogether, and just use a META
REFRESH=... tag in the HTML sent back? That way you don't have to worry
about the threads, and the client will be driving the refresh process,
instead of the server.
Beyond that, the only way I could imagine doing this would be via some form
of applet-servlet communication. Using plain HTML, I don't think you *can*
know when the client is "in" or "out" of the servlet.
Ted Neward
Patterns/C++/Java/CORBA/EJB/COM-DCOM spoken here
http://www.javageeks.com/~tneward
"I don't even speak for myself; my wife won't let me." --Me
-----Original Message-----
From: Duke Martin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, September 07, 1999 9:59 AM
Subject: correction
>I meant to say, how do I start a thread only when the client accesses the
>servlet and stop the thread when the client exits the servlet?
>
>Duke
>
>___________________________________________________________________________
>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
