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

Re: Beacon API

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 14 Feb 2013 12:34:28 +0000
Message-ID: <CADnb78jDBn=o=BOU9UO82-==BhQN2VUWBAaMXCZ5oaJ5XreGUw@mail.gmail.com>
To: "Reitbauer, Alois" <Alois.Reitbauer@compuware.com>
Cc: Jatinder Mann <jmann@microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>
On Thu, Feb 14, 2013 at 12:28 PM, Reitbauer, Alois
<Alois.Reitbauer@compuware.com> wrote:
> I do not see how this relates to the ping. If I understand the Ping
> correctly it send back the ping when a ling was clicked. The scenario here
> is totally different. An analytics tool - whether RUM or other analytics -
> collects a set of data like timing values etc. and then wants to beacon
> this data back to the server for further processing. I am not sure how to
> achieve this using the ping attribute.

Sure, you can achieve even more with an API as you propose, but the
idea is the same. The user navigates and the user agent is responsible
to do some phone-home thingie. My point is that ping="" failed thus
far, even though it's simpler conceptually.

Received on Thursday, 14 February 2013 12:35:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:58 UTC