On Fri, Aug 15, 2014 at 8:38 AM, Ben Maurer ben.mau...@gmail.com wrote:
Hey,
Thanks for writing this up!
So to the extent we are simply exposing http/2 semantics, this spec seems
pretty clear. Two questions that I have that aren't answered by the http/2
spec:
- What do we expect the
On Mon, Jul 28, 2014 at 10:14 AM, Anne van Kesteren ann...@annevk.nl
wrote:
On Mon, Jul 28, 2014 at 7:07 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 28 Jul 2014, Anne van Kesteren wrote:
On Wed, Jul 23, 2014 at 2:33 AM, Ian Hickson i...@hixie.ch wrote:
var mystyle = E('link', { rel:
On Tue, Jul 22, 2014 at 11:01 AM, Ben Maurer ben.mau...@gmail.com wrote:
On Tue, Jul 22, 2014 at 10:26 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 21 Jul 2014, Ben Maurer wrote:
(1) Allowing the user to specify parameters to Fetch. For example, a
user
could say:
script src=/my.js
On Tue, Jul 22, 2014 at 12:03 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 7/22/14, 2:57 PM, Ben Maurer wrote:
Nothing prevents a website from downloading content via fetch/XHR and
simply inserting that text into the DOM.
Yes, I know that. But we're trying to develop a better API so sites
http://fetch.spec.whatwg.org/#fetching says:
Otherwise, if response's body is non-null, run these substeps:
Every 50ms or whenever response's body's is pushed to, whichever is least
frequent and as long as response has no termination reason and end-of-file
has not been pushed, queue a task to
the Fetch API spec
in the Fetch spec document.
http://xhr.spec.whatwg.org/#the-send()-method
Takeshi
On Wed, Jul 23, 2014 at 6:31 AM, William Chan (陈智昌) willc...@chromium.org
wrote:
http://fetch.spec.whatwg.org/#fetching says:
Otherwise, if response's body is non-null, run
On Tue, Jul 15, 2014 at 2:06 PM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: willc...@google.com willc...@google.com on behalf of William Chan
(陈智昌) willc...@chromium.org
Can you explain this in more detail? AFAICT, the fundamental difference
we're talking about here is push
Just doublechecking...does this API allow the user agent to specify the
Content-Length in the request? Or is chunked transfer encoding required for
fetch()? I don't see any mention of a length attribute for streams in
https://whatwg.github.io/streams/ (let me know if I'm looking in the wrong
On Mon, Jul 14, 2014 at 8:56 AM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: whatwg whatwg-boun...@lists.whatwg.org on behalf of Domenic
Denicola dome...@domenicdenicola.com
Of these, 1 seems much nicer, based on my Node.js experience.
To be clearer as to why this is: stream
On Tue, Dec 3, 2013 at 4:16 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 17 Oct 2013, Michael Meier wrote:
Suppose I have a Websocket server and a WS client connected to it. The
client is a JS script in a browser offering the standard WS API. The
server produces data at a rate r1 and
On Tue, Dec 3, 2013 at 4:40 PM, William Chan (陈智昌) willc...@chromium.orgwrote:
On Tue, Dec 3, 2013 at 4:16 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 17 Oct 2013, Michael Meier wrote:
Suppose I have a Websocket server and a WS client connected to it. The
client is a JS script
On Tue, Dec 3, 2013 at 6:56 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 3 Dec 2013, William Chan (陈智昌) wrote:
If the server is generating data in response to some real-time query,
e.g. the results of a search on Twitter or some such, then what is the
server going to do
Hi, Chromium network dev here. I'm not an expert on the WebSocket API.
Pardon any stupid comments :)
On Thu, Oct 17, 2013 at 9:56 AM, Nicholas Wilson
nicho...@nicholaswilson.me.uk wrote:
Hello Michael,
If you're at all interested in the freshness of the data, you don't
want to use TCP as
On Sep 3, 2013 8:00 PM, Ryosuke Niwa rn...@apple.com wrote:
On Sep 3, 2013, at 5:01 PM, William Chan (陈智昌) willc...@chromium.org
wrote:
Hello folks. Sorry for the late response to several comments in this
mega-thread, I've mostly been traveling/vacationing for the past 2
months
Hello folks. Sorry for the late response to several comments in this
mega-thread, I've mostly been traveling/vacationing for the past 2 months.
A teammate asked me to look at this in case I had comments. I don't know
web dev issues very well, so I'm going to restrain myself from offering
many
Unless I am misunderstanding, SPDY will not solve this problem. SPDY uses
prioritized multiplexing of streams. Generally speaking, a browser will map
a single resource request to a single stream, which would prevent chunked
processing by the browser without multipart/mixed. One could imagine
situations it's not better to interleave response
data, as would be done by separate TCP connections, is indeed spot on.
On Mon, Dec 3, 2012 at 9:57 PM, Maciej Stachowiak m...@apple.com wrote:
On Dec 3, 2012, at 2:11 PM, William Chan (陈智昌) willc...@chromium.org
wrote:
Unless I am misunderstanding
17 matches
Mail list logo
