<br><br><div class="gmail_quote">On Fri, Nov 14, 2008 at 4:37 PM, Aaron Boodman <span dir="ltr"><<a href="mailto:aa@google.com">aa@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">On Fri, Nov 14, 2008 at 4:33 PM, Jonas Sicking <jonas@sicking.cc> wrote:<br>
> Hmm.. this makes a lot of sense for importScripts, but for XHR you probably<br>
> want the baseURI to be that of the opening page, since it's quite likely<br>
> that the opening page gave you a URI to open and process.<br>
<br>
</div>My expectation was that the base URI would always be the URI of the<br>
worker. I think of opening a worker a lot like starting a new process,<br>
or opening a new window. I would expect that the new process has its<br>
own base URI which is the same URI as the script it is running.</blockquote><div><br></div><div>My mental model for workers is a GUI less document almost. A dedicated</div><div>worker is akin to a nested iframe. A shared worker is akin to a top window</div>
<div>or tab. In that model, base is src of the resource loaded into the context.</div><div><br></div><div>> baseURI of the opening page</div><div><br></div><div>I don't think that would work well for shared workers.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<font color="#888888"><br>
- a<br>
</font></blockquote></div><br>