Hello Tim / Milt
Tim : I apologize for shooting off my mouth prior to checking simple things
like the header. The posteddate is 6/16 (same as original)
so, the duplicate post was probably due to a glitch on the server as pointed
out by Milt.
Milt : Thanks for pointing it out to me. :)
-Rajesh
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
On Thu, 22 Jun 2000, SHEDDE, RAJESH wrote:
> Is this some kind of a joke ????
>
> The exact same question was posted by the same person on 6/16/2000 . There
were
> 3-4 responses to it too. A very detailed
> response by Nic Ferrier included. And now again 6 days later the question is
> re-posted as a fresh question. It would be advisable not to indulge
> in such practices. What is likely to happen is your name/email id would be
added
> to a personal ignore list and future questions
> would go unanswered.
[ ... ]
Hold on a sec -- you recognize that it is the exact same question
posted by the exact same person -- doesn't it seem strange to you that
they would do that intentionally? Could possibly something else have
caused this to happen? In fact, if you check the headers, you'll see
that it was the exact same post. Basically, it looks very much like
there was some kind of glitch on the mailing list server on Sun's end
that sent out a bunch of messages again. And this is not the first
time this has happened. Hopefully this won't last long, because it is
annoying, but there haven't been much indications lately that someone
from Sun is following this list (e.g. there's the bounced messages
from bad addresses that get sent out in reply whenever someone posts
to the list).
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> 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
