- From: Adrian Cole <adrian.f.cole@gmail.com>
- Date: Tue, 6 Jan 2015 18:57:23 -0800
- To: Patrick McManus <pmcmanus@mozilla.com>
- Cc: Stefan Eissing <stefan.eissing@greenbytes.de>, HTTP Working Group <ietf-http-wg@w3.org>
> client opens a stream indicating its interested in an event stream.. the > server may/may not provide a response but it leaves that stream open for the > duration of time it might push. When it pushes events (represented by a > request/response pair) it associates the new even streams with the client > stream. There can be N of these events in parallel, which makes it > considerably nicer than long polling. Whenever the server decides it is done > pushing things it can close the odd stream.. or the client can stream reset > the odd stream if it decides its done first. Bravo. Very succinct explanation of how to implement what people often think push would do. Good job, Patrick!
Received on Wednesday, 7 January 2015 02:57:50 UTC