W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: [websockets] Binary support changes

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Mon, 30 May 2011 18:22:17 -0400
Message-ID: <BANLkTimeyVEa3RDPjRK9_rcCcejV5gjxZg@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>, Adrian Bateman <adrianba@microsoft.com>
On Mon, May 30, 2011 at 3:20 AM, Simon Pieters <simonp@opera.com> wrote:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12805
>
> I agree, using interface object complicates things when working across
> globals (you basically need to pass along the global as well which is uglier
> than using a string).

More than that, basically no authors are even going to understand
what's happening here.  They'll just use iframes for something and
then it will mysteriously fail to work.  The cause of failure is
pretty much totally incomprehensible unless you're a real JavaScript
guru.  I ran into this issue a while ago, and it took me a long time
to figure out what's going on, despite the fact that I'm vastly more
familiar with ECMAScript than 99.9% of web authors and had the help of
#whatwg.  No API should rely on two different interface objects being
equal unless absolutely necessary.
Received on Monday, 30 May 2011 22:23:05 GMT

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