RE: [Workers] Worker same-origin and usage in JS libraries...

2012-12-03 Thread Travis Leithead
From: Ian Hickson [mailto:i...@hixie.ch] On Tue, 17 Jul 2012, Ian Hickson wrote: My plan is to make it so that cross-origin URLs start cross-origin workers. The main unresolved question is how to do this in an opt-in manner. The best idea I've come up with so far is having scripts that

Re: [Workers] Worker same-origin and usage in JS libraries...

2012-11-29 Thread Ian Hickson
On Tue, 17 Jul 2012, Ian Hickson wrote: My plan is to make it so that cross-origin URLs start cross-origin workers. The main unresolved question is how to do this in an opt-in manner. The best idea I've come up with so far is having scripts that want to opt-in to being run in such a way

Re: [Workers] Worker same-origin and usage in JS libraries...

2012-11-29 Thread Ojan Vafai
On Thu, Nov 29, 2012 at 4:31 PM, Ian Hickson i...@hixie.ch wrote: On Tue, 17 Jul 2012, Ian Hickson wrote: My plan is to make it so that cross-origin URLs start cross-origin workers. The main unresolved question is how to do this in an opt-in manner. The best idea I've come up with so far

Re: [Workers] Worker same-origin and usage in JS libraries...

2012-07-17 Thread Ian Hickson
On Tue, 6 Dec 2011, Jonas Sicking wrote: On Tue, Dec 6, 2011 at 5:05 PM, Travis Leithead travis.leith...@microsoft.com wrote: A new scenario just came to my attention that I thought I might pose to the list. Given the current same-origin restrictions on new Worker(), it is problematic for

Re: [Workers] Worker same-origin and usage in JS libraries...

2012-07-17 Thread Bronislav Klučka
On 17.7.2012 23:53, Ian Hickson wrote: My plan is to make it so that cross-origin URLs start cross-origin workers. The main unresolved question is how to do this in an opt-in manner. The best idea I've come up with so far is having scripts that

Re: [Workers] Worker same-origin and usage in JS libraries...

2012-07-17 Thread Ian Hickson
On Wed, 18 Jul 2012, Bronislav Klu�~Mka wrote: Since script is loaded using HTTP, why not use already defined CORS headers on server side while serving those scripts? CORS is the wrong semantic. It's not origin A is allowed to read content from origin B, it's origin A is allowed to cause

Re: [Workers] Worker same-origin and usage in JS libraries...

2012-07-17 Thread Bronislav Klučka
On 18.7.2012 1:05, Ian Hickson wrote: And if you want it to be defined in JS file itself, I'll suggest use strict approach: file --- Access-Control-Allow-Origin: *; (function(){ use strict; var x = 5; })();

[Workers] Worker same-origin and usage in JS libraries...

2011-12-06 Thread Travis Leithead
A new scenario just came to my attention that I thought I might pose to the list. Given the current same-origin restrictions on new Worker(), it is problematic for Worker usage by any JS libraries on a CDN. A site using a CDN simply provides an absolute URL reference to the library, and it is