Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?
On Thu, Aug 14, 2014 at 6:20 AM, Takeshi Yoshino tyosh...@google.com wrote: We're implementing Streams API and integration of it and XHR experimentally in Blink. I think the question is not so much how far along XMLHttpRequest and fetch() are, but how far along streams is. E.g. a chat I had yesterday http://krijnhoetmer.nl/irc-logs/whatwg/20140813#l-592 suggests there's still many things to sort through. -- http://annevankesteren.nl/
Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?
Streams API itself still has many issues, right. We'd like to continue prototyping in Blink anyway to provide feedback to the spec as browser developer's point of view, but if we're sure that we won't add it to XHR, we want to stop the work on XHR (both spec and impl) at some early stage after figuring out very basic issues and focus on the Fetch. Takeshi On Thu, Aug 14, 2014 at 4:03 PM, Anne van Kesteren ann...@annevk.nl wrote: On Thu, Aug 14, 2014 at 6:20 AM, Takeshi Yoshino tyosh...@google.com wrote: We're implementing Streams API and integration of it and XHR experimentally in Blink. I think the question is not so much how far along XMLHttpRequest and fetch() are, but how far along streams is. E.g. a chat I had yesterday http://krijnhoetmer.nl/irc-logs/whatwg/20140813#l-592 suggests there's still many things to sort through. -- http://annevankesteren.nl/
Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?
On Thu, Aug 14, 2014 at 9:19 AM, Takeshi Yoshino tyosh...@google.com wrote: We'd like to continue prototyping in Blink anyway to provide feedback to the spec as browser developer's point of view, but if we're sure that we won't add it to XHR, we want to stop the work on XHR (both spec and impl) at some early stage after figuring out very basic issues and focus on the Fetch. I recommend putting all your energy on Fetch and Streams then. We can still add features to XMLHttpRequest if there's compelling reasons (e.g. we hit deployment issues with fetch()), but we should not put our focus there. -- http://annevankesteren.nl/
Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?
On Thu, Aug 14, 2014 at 4:29 PM, Anne van Kesteren ann...@annevk.nl wrote: On Thu, Aug 14, 2014 at 9:19 AM, Takeshi Yoshino tyosh...@google.com wrote: We'd like to continue prototyping in Blink anyway to provide feedback to the spec as browser developer's point of view, but if we're sure that we won't add it to XHR, we want to stop the work on XHR (both spec and impl) at some early stage after figuring out very basic issues and focus on the Fetch. I recommend putting all your energy on Fetch and Streams then. We can still add features to XMLHttpRequest if there's compelling reasons (e.g. we hit deployment issues with fetch()), but we should not put our focus there. Thanks. I'd like to hear opinions from others too. BTW, Anne, as the fetch() is planned to be available in non-ServiceWorker scopes, could you please do either of: a) discuss issues about fetch() at public-webapps@ b) add a link to https://github.com/slightlyoff/ServiceWorker/labels/fetch in http://fetch.spec.whatwg.org/ as well as the link to public-webapps@ I guess you don't want to do (a). (b) is fine. Then, readers of http://fetch.spec.whatwg.org/ can easily know that discussions about fetch() are happening at the ServiceWorker issue tracker even if he/she is not familiar with ServiceWorker, and join it if want.
Re: [Streams API] Add load-using-streams functionality to XHR or only to Fetch API?
On Thu, Aug 14, 2014 at 9:39 AM, Takeshi Yoshino tyosh...@google.com wrote: I guess you don't want to do (a). (b) is fine. Then, readers of http://fetch.spec.whatwg.org/ can easily know that discussions about fetch() are happening at the ServiceWorker issue tracker even if he/she is not familiar with ServiceWorker, and join it if want. That makes sense, done. I'm not sure why I would want to encourage readers to post about Fetch on yet another mailing list so I have not added this mailing list. -- http://annevankesteren.nl/
[Streams API] Add load-using-streams functionality to XHR or only to Fetch API?
We're implementing Streams API [1] and integration of it and XHR [2] experimentally in Blink [3][4]. Anne suggested that we look into adding new fetch-layer features to the Fetch API [5][6] rather than XHR in Blink mailing list (blink-dev) [6]. There's a concern if we can ship the Fetch API to non-ServiceWorker scope soon [7]. I'd like to hear your opinions on these issues: - add the feature only to the Fetch, or both XHR and Fetch? - how the integration should be done? Thanks [1] https://github.com/whatwg/streams [2] http://xhr.spec.whatwg.org/ [3] https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/core/streams/ [4] https://github.com/tyoshino/streams_integration/blob/master/README.md [5] http://fetch.spec.whatwg.org/#fetch-method [6] http://fetch.spec.whatwg.org/#body-stream-concept [7] https://groups.google.com/a/chromium.org/d/msg/blink-dev/GoFbe0yLO50/SXpYMdYn0A4J [8] https://groups.google.com/a/chromium.org/d/msg/blink-dev/GoFbe0yLO50/vviGEQ5Z-KoJ
