W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2013

Re: [Beacon] Review of current spec

From: Chase Douglas <chase@newrelic.com>
Date: Thu, 14 Nov 2013 14:14:15 -0800
Message-ID: <CAKNWE6Ex49w2RMAgsvGeTmH5fre8YKrWT1XstBmJe4U523CG9Q@mail.gmail.com>
To: Ilya Grigorik <igrigorik@google.com>
Cc: Arvind Jain <arvind@google.com>, "Reitbauer, Alois" <Alois.Reitbauer@compuware.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
So you're proposing a different spec and api that would simply compress
data like:

var zipped = window.compress('Please compress this string!');

And zipped would be a Blob? That would definitely be handy if we could get
such a thing.


On Thu, Nov 14, 2013 at 2:10 PM, Ilya Grigorik <igrigorik@google.com> wrote:

>
> On Thu, Nov 14, 2013 at 9:57 PM, Arvind Jain <arvind@google.com> wrote:
>
>> OK. Dumb question: how do we compress the payload in sendBeacon()
>> (assuming we know the server can handle it)?
>>
>
> Therein lies the problem - you can't, at least not via any standard API.
> There are pure JS implementations out there, but that's suboptimal... While
> we're on the subject, having such an API would be very beneficial for XHR,
> WebSockets, and this case as well.
>
> I don't think this is something we need to tackle as part of Beacon API.
> Instead, we should solve it at a higher layer... since we already accept
> Blob, it would work without any modifications once such an API is available.
>
Received on Thursday, 14 November 2013 22:14:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:37 UTC