Don't be so quick. It is possible to do what the previous poster suggested about writing space. Basically after writing the whole page out you don't quit writing but keep sending stuff (space). The problem with this of course that you will have all these open IOs going.
There was a version of IE that didn't work properly with this though. It would break the session. Maybe an invisible applet on the client that nudges the server every 30 seconds or so is a better idea? This way you know where client to within that interval. I'm not advocating these things. I think that when you need to employ elaborate schemes like that it's time to move into writing client application but then again I enjoy some of those same online applications that allow me to check my sliding 401k :) Go figure. d. Galbreath, Mark wrote: > 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 > > > -- David Mossakowski [EMAIL PROTECTED] Instinet Corporation 212.310.7275 ******************************************************************************* <<Disclaimer>> This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL or both. This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return mail and permanently deleting the copy you received. Thank you. ******************************************************************************* ___________________________________________________________________________ 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
