We're using a servlet to log web accesses. Basically our servlet is called
via an image tag in the following sequence:
1) The arguments passed to the servlet are pulled out of the request
object.
2) The ServletOutputStream is opened
3) An image is output to the ServletOutputStream
4) The ServletOutputStream is closed
5) The arguments are processed by our servlet and logged to a database.
The servlet is coded in such a way that the processing before the image is
output and the outputstream is closed is minimal. I'd think that the servlet
*should* return a response very quickly. Due to the fact that it's taking a
long time, I'm wondering what closes the connection to an end-user's web
browser. I'm inclined to think that ServletOutputStream.close() doesn't do it.
If not, how can we speed this up and still get our processing done?
In order to close the connection to a browser as fast as possible, do we have
to set the ServletResponse object == null or something to force it to go out of
scope?
Thanks for your help,
-Tim
___________________________________________________________________________
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
