Is it appropriate to declare an
HttpServlet's service() [or doGet()/doPost()] methods synchronized so that I
can block additional requests as long as the servlet's life cycle has not
been terminated (i.e. it has been destroy()'ed)?
I am trying to write a file
copy routine that runs as a background thread in a servlet, initiated by the
first request to the servlet, and destroyed once the thread is completed upon
receipt of a progress check from the client which initiates the servlet.
The servlet calls itself repetitively (using setHeader("refresh", ...)),
reporting progress until the thread is completed.
Also, can a servlet destroy()
itself after the the response has been sent? If so, how would it be
accomplished?
Thanks for any insight in
advance...
Jason
Coward
email [EMAIL PROTECTED]
