Re: Overlap between StreamReader and FileReader from Takeshi Yoshino on 2013-09-13 (public-webapps@w3.org from July to September 2013)

From: Takeshi Yoshino <tyoshino@google.com>
Date: Fri, 13 Sep 2013 21:23:30 +0900
To: Aymeric Vitte <vitteaymeric@gmail.com>
Cc: Isaac Schlueter <i@izs.me>, Jonas Sicking <jonas@sicking.cc>, Austin William Wright <aaa@bzfx.net>, Domenic Denicola <domenic@domenicdenicola.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <CAH9hSJYpDWUWOtUbMr9ObAegE+hdrzyZ3uQuA_02yUTPsoe6rw@mail.gmail.com>

On Fri, Sep 13, 2013 at 6:08 PM, Aymeric Vitte <vitteaymeric@gmail.com>wrote:

> Now you want a stream interface so you can code some js like mspack on top
> of it.
>
> I am still missing a part of the puzzle or how to use it: as you mention
> the stream is coming from somewhere (File, indexedDB, WebSocket, XHR,
> WebRTC, etc) you have a limited choice of APIs to get it, so msgpack will
> act on top of one of those APIs, no? (then back to the examples above)
>
> How can you get the data another way?
>

Do you mean that those data producer APIs should be changed to provide
read-by-delta-data, and manipulation of data by js code should happen there
instead of at the output of Stream?

Received on Friday, 13 September 2013 12:24:22 UTC