W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Fwd: Data compression APIs?

From: timeless <timeless@gmail.com>
Date: Mon, 30 Jan 2012 09:11:10 -0500
Message-ID: <CANAYn0G-W0QWK+ngw=RbQiCEChaF1fG+vLV+gMjycQvbO7LEsg@mail.gmail.com>
To: WebApps <public-webapps@w3.org>
Since webapps is currently rechartering, is this something it wants to consider?

Note that I'm not a member of webapps at this time.

There have been some requests for zip support [1], and probably less
relevant for xhr [2]. Note that the use case I'm forwarding [3]
requires support for both compression and decompression.

[1] http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0567.html
[2] http://lists.w3.org/Archives/Public/public-webapps/2008JulSep/0595.html
[3] http://lists.w3.org/Archives/Public/public-identity/2012Jan/0002.html

---------- Forwarded message ----------
From: Mitch Zollinger <mzollinger@netflix.com>
Date: Wed, 25 Jan 2012 17:11:57 -0800
Subject: Data compression APIs?
To: "public-identity@w3.org" <public-identity@w3.org>

In designing the technology that satisfies the use case doc posted
previously (http://www.w3.org/wiki/NetflixWebCryptoUseCase) it would
appear that we need to support compression / decompression APIs.

The reason is that for our "MsgSec" protocol, we encrypt every message
going over the wire and since encrypted data cannot be compressed, the
compression has to happen before encryption. Therefore standard things
like HTTP gzip compression will not work.

What we're looking for is something along the lines of:

   function compress(data, algorithm)
   function uncompress(data, algorithm)

where algorithm is one of the standard ones (gzip, bzip2, etc.)

Is this the right forum for looking at this type of functionality?

Mitch



-- 
Sent from my mobile device
Received on Monday, 30 January 2012 14:11:38 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT