W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: {Spam?} Re: [xhr]

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 3 Sep 2014 19:25:50 +0000 (UTC)
To: Anne van Kesteren <annevk@annevk.nl>
cc: Brendan Eich <brendan@secure.meer.net>, Charles McCathienevile <chaals@yandex-team.ru>, Robert Hanson <hansonr@stolaf.edu>, WebApps WG <public-webapps@w3.org>
Message-ID: <alpine.DEB.2.00.1409031924040.2532@ps20323.dreamhostps.com>
On Wed, 3 Sep 2014, Anne van Kesteren wrote:
> On Wed, Sep 3, 2014 at 7:07 PM, Ian Hickson <ian@hixie.ch> wrote:
> > Hear hear. Indeed, a large part of moving to a "living standard" model is
> > all about maintaining the agility to respond to changes to avoid having to
> > make this very kind of assertion.
> See 
> http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/thread.html#msg232 
> for why we added a warning to the specification. It was thought that if 
> we made a collective effort we can steer people away from depending on 
> this.

The text of the warning seems fine to me. It doesn't make any assertions 
about the future as far as I can tell; it just discourages use of a 
feature and says that we hope to remove it. If we are ever to remove 
something as widely used as sync XHR, this kind of advocacy seems like a 

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 3 September 2014 19:26:14 UTC

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