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

Re: Beacon API

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 15 Feb 2013 11:06:51 +0000
Message-ID: <CADnb78iwZGHwVe-h8pCQkN5jS+jApeUDF-BMm711GmQUixcGAw@mail.gmail.com>
To: Ilya Grigorik <igrigorik@google.com>
Cc: public-webapps@w3.org
On Fri, Feb 15, 2013 at 12:21 AM, Ilya Grigorik <igrigorik@google.com> wrote:
> A lot of the discussion so far focused on the async analytics beacon +
> unload use case. However, while this is an important case to consider, let's
> not constrain this proposal to "on unload" case only.

Just to be clear. I understand why we'd want this. I'm a) wondering
why it'll be successful this time given it has the same
characteristics as ping="" b) asking about the desired timeframe given
the highly likely introduction of a new Future-based API for fetching.


-- 
http://annevankesteren.nl/
Received on Friday, 15 February 2013 11:07:25 GMT

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