- From: Florian Bösch <pyalot@gmail.com>
- Date: Mon, 6 May 2013 13:30:03 +0200
- To: Robin Berjon <robin@w3.org>
- Cc: Webapps WG <public-webapps@w3.org>
- Message-ID: <CAOK8ODhMb4KBLuSqnB6VzbMzdaGynO2G1n1Jc4J=kNuYJB5fyQ@mail.gmail.com>
The main reason to use an archive (other than the space-savings) for me is to be able to transfer tens of thousands of small items that go into producing WebGL applications of non trivial scope. On Mon, May 6, 2013 at 1:27 PM, Robin Berjon <robin@w3.org> wrote: > On 03/05/2013 21:05 , Florian Bösch wrote: > >> It can be implemented by a JS library, but the three reasons to let the >> browser provide it are Convenience, speed and integration. >> > > Also, one of the reasons we compress things is because they're big.* > Unpacking in JS is likely to mean unpacking to memory (unless the blobs are > smarter than that), whereas the browser has access to strategies to > mitigate this, e.g. using temporary files. > > Another question to take into account here is whether this should only be > about zip. One of the limitations of zip archives is that they aren't > streamable. Without boiling the ocean, adding support for a streamable > format (which I don't think needs be more complex than tar) would be a big > plus. > > > > * Captain Obvious to the rescue! > > > -- > Robin Berjon - http://berjon.com/ - @robinberjon >
Received on Monday, 6 May 2013 11:30:56 UTC