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 10:04:09 +0000
Message-ID: <CADnb78jAfSaL2T69F-yKoVR3VMyRifW06kSq2qTAtdnPGLGV4Q@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 9:55 AM, Reitbauer, Alois
<Alois.Reitbauer@compuware.com> wrote:
> You are right we would not need any progress events and you are also
> typically not interested in the response. The server should normally reply
> only with a no content reply. Conceptually this reply would not be needed,
> however, HTTP requires it. You can think of this type of interaction like
> sending an UDP packet. You want it to be send and delivered at best
> effort.

Are you sometimes interested in the response? Kind of makes a difference.

Also, how is this different from
http://www.whatwg.org/specs/web-apps/current-work/#ping Especially if
we make this a dedicated feature in some way it seems all the same
considerations apply and that feature has thus far not been hugely
successful.


-- 
http://annevankesteren.nl/
Received on Thursday, 14 February 2013 10:04:41 GMT

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