Hi,
I’m wondering if there is any work in progress to define an API for JavaScript
clients to detect that an HTTP/2 server has pushed content, and to control the
“half closed” vs “closed” state of HTTP/2 streams (to control whether or not a
server can push content).
Use Case
The use-case I
On 20 Feb 2015, at 10:48, Brendan Long s...@brendanlong.com wrote:
The obvious question to ask is “why not just poll the server”? The answer its
that live streaming latency depends (among other things) on how quickly you
poll. Unless you can perfectly predict when the server will have an
On Feb 20, 2015, at 11:53 AM, Kornel Lesiński kor...@geekhood.net wrote:
For server push we already have Server-Sent Events:
https://html.spec.whatwg.org/multipage/comms.html#server-sent-events
https://html.spec.whatwg.org/multipage/comms.html#server-sent-events
Using an entirely
On 18.2.2015 0:15, Barry Smith wrote:
I have read where the W3C has made the hgroup element obsolete,
http://www.w3.org/html/wg/drafts/html/master/obsolete.html#non-conforming-features
. I see the specification is still in the WHATWG HTML: The Living
Standard specifications. Are there any
Hi Ryan,
Thanks for writing this up. I know you already know this, but I wanted to
publically declare my support as one of the MSE editors. While I wish we
didn't need this, I can understand the concerns of content providers and I
think this is a reasonable compromise.
Aaron
On Thu Feb 19 2015
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Brendan Long
It’s not clear to me how we would cancel a pushed stream, or retrieve
streaming body data without waiting for the request to completely finish.
Working on that:
- http://streams.spec.whatwg.org/
-
