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

Re: Shared workers - use .source instead of .ports[0] ?

From: Simon Pieters <simonp@opera.com>
Date: Wed, 11 Apr 2012 08:11:22 +0200
To: "David Levin" <levin@google.com>, "Jonas Sicking" <jonas@sicking.cc>
Cc: "Andrew Wilson" <atwilson@google.com>, "Jarred Nicholls" <jarred@webkit.org>, "public-webapps@w3c.org" <public-webapps@w3c.org>
Message-ID: <op.wck7g8f1idj3kv@simons-macbook-pro.local>
On Wed, 11 Apr 2012 07:56:48 +0200, Jonas Sicking <jonas@sicking.cc> wrote:

> On Tue, Apr 10, 2012 at 10:44 PM, David Levin <levin@google.com> wrote:
>> What is the backwards compatibility story for websites already using
>> SharedWorkers with the interface that has been in the spec for over a  
>> year
>> now?
>>
>> There are sites using them. For example, Google Docs uses them and  
>> Google
>> Web Toolkit exposes them.

Either we get them updated to the new API or we keep ports[0] around for  
compat. If we can't get rid of ports[0], I see less value in making the  
change at all since some scripts will use .source and other will use  
.ports[0], which seems pretty confusing.

Google Docs can hopefully be updated before implementations ship with  
this, but GWT might be more problematic since there may be legacy apps  
around with unknown update shedule...

> As far as I can see there are no backwards compat breaking changes
> proposed. Are there any particular parts you are worried about?

I proposed setting ports to null.

-- 
Simon Pieters
Opera Software
Received on Wednesday, 11 April 2012 06:11:55 GMT

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