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

Re: Beacon API

From: Dave Methvin <dave.methvin@gmail.com>
Date: Wed, 13 Feb 2013 13:18:01 -0500
Message-ID: <CACnq-uL8ZLEzEVDO55hc3kgzAaXL9pFGStDx01uLaLtsoDkYHA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Jatinder Mann <jmann@microsoft.com>, "annevk@opera.com" <annevk@opera.com>, "public-webapps@w3.org" <public-webapps@w3.org>, "Reitbauer, Alois (Alois.Reitbauer@compuware.com)" <Alois.Reitbauer@compuware.com>
On Wed, Feb 13, 2013 at 11:45 AM, Tab Atkins Jr.

> I started a thread last year in WHATWG about this subject, though from
> a slightly different angle:
> <http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-May/035686.html
> >.

A new simple API sounds like the best solution. Adding a sufficiently
limited beacon into XHR would seem to involve a lot of special cases, since
you don't want the response, callbacks, CORS, etc. but the requests
themselves would need to stay around after the page is done.

It might be handy to have a method property to specify get/post and I'd
prefer a name like unloadRequest since it's making a request and not
setting a handler. Finally, is script-only capability sufficient or does it
make sense to also have some form of markup specifying a link to be visited
when the page unloads? </bikeshed>
Received on Wednesday, 13 February 2013 18:18:29 UTC

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