On Tue, May 7, 2013 at 8:09 AM, Jonas Sicking <jonas@sicking.cc> wrote:
> > You're arguing for allowing accessing files inside ZIPs by URL, which
> means
> > you're going to have to do the work anyway, since you'd be able to
> create a
> > blob URL, reference a file inside it using XHR, and get a Blob as a
> result.
> > This is a small subset of that.
>
> No, the work to write and maintain an API for ZIP
> compress/decompression is pretty orthogonal, implementation-wise, to a
> protocol handler for ZIP decompression.
>
In order to implement zip you would use one of the ready made libraries
supporting it, such as libzip (http://www.nih.at/libzip/index.html),
minizip (http://www.winimage.com/zLibDll/minizip.html),
Both libraries (and any other library you might encounter) already defines
an API and an implementation. In order to support ZIP URLs you would use
the API. In order to support a JS zip API, you would expose the API. These
are not orthogonal, they are correlated.