Still don't think you guys know what you are talking about.  You can't do
this with HTTP!  Think: "request - response."  Aaaahhhh...now you're getting
it!

-----Original Message-----
From: Michael Peceny [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 08, 2002 6:47 AM

If you used the "space writing" method, do not forget to flush
the output stream -- otherwise, the output data is buffered and
only sent to the client once the buffer (default 8kB, I think)
is full.

Note that this is slow, though -- contacting the client every
few seconds to determine whether they are still waiting for you
to send data can cost a lot of time (think of the network between
your server and the client).

Michael


> I'd be interested in knowing how this works with HTTP.  Where
> is your output
> stream going?
[...]
> > is there a way to check if the client has a connection or he/she has
> closed
> > the connection using the stop button .....
>
> Yes. Trying to write to the output stream would return an
> IOException. I
> could write a white space in a separate thread every few
> seconds and if an
> exception occurs, I stop processing.

___________________________________________________________________________
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

Reply via email to