> Kalnichevski, Oleg wrote: > > I may be wrong here, but let me express my personal opinion on this > > matter. Please bear in mind HTTP protocol has been designed to be > > stateless, request/response oriented (with cookies being a very > > clumsy attempt at adding session persistence later on). I doubt that > > HTTP protocol is well suited for implementing any sort of > > notification channel. I suggest you reconsider your design and > > probably use good ol' polling instead, rather than getting very > > creative with the use of chunk encoding > > This is my oppinion about this matter as well. Even if you manage to > read the chunked data, you will most probably run into problems with the > web server (not your server side application) closing the connection > after a certain idle time.
Fredrik Just do a blocking read, which unblocks with a "no events" every minute or so, or when an event arrives. The client can then go go straight back to the server with another "is there any more events?" call. It's .... (mumble,mumble) .... what we do ;) Cheers, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
