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

Re: "Officially" deprecating main-thread synchronous XHR?

From: Scott González <scott.gonzalez@gmail.com>
Date: Tue, 18 Feb 2014 13:14:48 -0500
Message-ID: <CAO8i3ifi+ZSAjC9m-QaTJ9ECqgBR_P0kSw+sd9NVqqco=zxorg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-webapps <public-webapps@w3.org>
I believe Beacon will address the use cases for developers currently using
sync XHR in beforeunload/unload/pagehide. I don't think any browser should
warn about sync XHR in these cases until they support Beacon.

I've discussed this will Olli in IRC, but I've been pushing for jQuery to
deprecate jQuery.ajax() and replace it with transport-specific methods such
as jQuery.xhr() and jQuery.jsonp(). jQuery.xhr() would not have support for
sync requests. After a few years of pushing for this, it looks like it
might finally happen. This would go a long way toward evangelizing the
avoidance of sync requests.

On Fri, Feb 7, 2014 at 12:38 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 2/7/14 12:32 PM, Scott González wrote:
>> What about developers who are sending requests as the page is unloading?
> Does Beacon address their use cases?  If not, what are the use cases?
> -Boris
Received on Tuesday, 18 February 2014 18:15:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:22 UTC