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

Re: [Beacon] spec feedback + few suggestions

From: Chase Douglas <chase@newrelic.com>
Date: Wed, 30 Oct 2013 12:04:57 -0700
Message-ID: <CAKNWE6E_br+zjuma90Tgkbv5c6geXf6RNg7RHs6RcjDoqeH_hA@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: Ilya Grigorik <igrigorik@google.com>, public-web-perf <public-web-perf@w3.org>, Jonas Sicking <jonas@sicking.cc>
On Wed, Oct 30, 2013 at 11:36 AM, Jatinder Mann <jmann@microsoft.com> wrote:

> > Beacon API should limit size of send payload to <TBD> KB****
>
> I agree that we should add a limit. Iíve heard feedback where some folks
> were hoping to use this API to do large background uploads. Adding a limit
> would prevent this kind of abuse of the API. What is a decent limit?
>

Why is it the spec's responsibility to set a limit? Shouldn't this be up to
the website developer to decide what is reasonable? A W3C spec just isn't
the right place to try to limit the functionality of the web in the name of
safety.

I think it makes sense that browser implementations have limits. But
implementation-specific variability can change as needed over time. Specs
can't be changed as easily.

Could we add a method for scripts to ask what the implementation limits are
(both size and frequency)? We're using query strings to send data in
certain places, and figuring out what will fit into query strings is
annoying.

Thanks!
Received on Wednesday, 30 October 2013 19:05:25 UTC

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