On 5/25/05, Mladen Turk <[EMAIL PROTECTED]> wrote: > Nikola Milutinovic wrote: > > [EMAIL PROTECTED] wrote: > >> > > > > Then you're messing it up. HTTP has no paradigm of a session, which is > > what you need here. HTTP has a very clear request/response model. It is > > not designed to hold the HTTP channel open indefinitely and will break > > off after a timeout. Timeout is configurable both on client and server > > sides. So, you can easily get server timeout or client timeout on the > > connection. And that is definitely not good for a realtime application :-) > > > > Sure all that is in place, but OTOH the http keep-alive connection *can* > be opened for several hours or days. > HTTP/1.1 uses persistent connections by default and you must explicitly > add the 'Connection: close' in the header. > Without that, things like internet radio for example would be a > pure wish :)
Do internet radio and the like actually use the HTTP protocol though? I'm by no means an expert but I would have expected them to use their own protocol to handle the streaming? -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
