- From: Jonas Sicking <jonas@sicking.cc>
- Date: Wed, 17 Jul 2013 11:05:43 -0700
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: Takeshi Yoshino <tyoshino@google.com>, Feras Moussa <feras.moussa@hotmail.com>, Travis Leithead <travis.leithead@microsoft.com>, Alex Russell <slightlyoff@google.com>, "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
On Wed, Jul 17, 2013 at 10:47 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Tue, Jul 16, 2013 at 11:10 PM, Jonas Sicking <jonas@sicking.cc> wrote: >> Reading any format that contains textual data. I.e. things like HTML, >> OpenDocument, pdf, etc. While many of those are compressed, it seems >> likely that you could pass a stream through a decompressor which >> produces a decompressed stream. > > Yeah, extending APIs for such features to support streams seems better > than adding support for all of them on Stream. Letting Stream just be > a low-level primitive for a stream of bytes seems good enough. What do you mean by "such features"? Are you saying that a Stream zip decompressor should be responsible for both decompressing as well as binary->text conversion? And thus output something other than a Stream? / Jonas
Received on Wednesday, 17 July 2013 18:06:41 UTC