W3C home > Mailing lists > Public > public-digipub-ig@w3.org > December 2015

Re: FYI: gzip/zip in the browsers...

From: Daniel Weck <daniel.weck@gmail.com>
Date: Tue, 22 Dec 2015 18:09:14 +0000
Message-ID: <CA+FkZ9Fw+Cnc0YCakOjsqwYZWAirnE++=4TQrKt=ZnsTqVVagA@mail.gmail.com>
To: Ivan Herman <ivan@w3.org>
Cc: W3C Digital Publishing IG <public-digipub-ig@w3.org>
A browser-native "zip" API would be useful (i.e. support for file-tree
read+write, and per-resource deflate/inflate), preferably available in
Web Workers as well as in the regular window / DOM context. In Readium
a third-party Javascript library is used to decompress packed EPUB
resources on-the-fly (via HTTP byte-range requests), and also to
expand whole EPUB archives into local storage.

A successful example of the "make it browser-native" pattern is the
window.crypto API, which implements computationally-expensive
cryptography routines that have been available in pure-Javascript
libraries for some time:


On Tue, Dec 22, 2015 at 8:28 AM, Ivan Herman <ivan@w3.org> wrote:
> There are some discussions on having natively zip-like facilities in the
> browser:
> http://discourse.wicg.io/t/need-for-gzip-deflate-api/1237
> http://discourse.wicg.io/t/a-zip-api-in-the-browser/14
> I have no idea whether there is more than just discussions at this point,
> though.
> Ivan
> ----
> Ivan Herman, W3C
> Digital Publishing Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Tuesday, 22 December 2015 18:10:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:20 UTC