W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

[Streams API] Add load-using-streams functionality to XHR or only to Fetch API?

From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 14 Aug 2014 13:20:44 +0900
Message-ID: <CAH9hSJYNckMs=Vyg_JfNTLaEnS3OnbyeB=qeCCXbKwuU-QDDHQ@mail.gmail.com>
To: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>, Anne van Kesteren <annevk@annevk.nl>
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?


[1] https://github.com/whatwg/streams
[2] http://xhr.spec.whatwg.org/
[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
Received on Thursday, 14 August 2014 04:21:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC