Re: File API: reading a Blob

Sorry to interfer then but your discussion with Arun seems to have no 
point if streams are there.

But some points I mentioned have, whether it's really linked to the 
initial subject or not.

The fact is that most of the W3C groups impacted by streams (File, 
indexedDB, MSE, WebRTC, WebCrypto, Workers, XHR, WebSockets, Media 
Stream, etc, I must forget a lot here) seem not to care a lot about it 
and maybe just expect streams to land in the right place in the APIs 
when they are available, by some unknown magic.

I still think that the effort should start from now for all the APIs (as 
well as the implementation inside browsers, which apparently has started 
for Chrome, but Chrome was supposed to have started some implementation 
of the previous Streams APIs, so it's not very clear), and that it 
should be very clearly synchronized, disregarding vague assumptions from 
the groups about low/high level and Vx releases, eluding the issue.


Le 01/09/2014 11:14, Anne van Kesteren a écrit :
> On Thu, Aug 28, 2014 at 2:15 AM, Aymeric Vitte <vitteaymeric@gmail.com> wrote:
>> I have contributed to streams already, of course it will solve most of what
>> is being discussed here but when? And then what's the point of this
>> discussion?
> This discussion between me and Arun is about how to describe various
> algorithms in File API and Fetch, ideally enabling APIs on top of
> those low-level descriptions later on. But it is about describing the
> behavior of existing APIs in more detail.
>
>

-- 
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

Received on Wednesday, 3 September 2014 22:02:43 UTC