<div class="gmail_quote">On Tue, Aug 18, 2009 at 1:22 PM, Jonas Sicking <span dir="ltr"><jonas@sicking.cc></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Aug 18, 2009 at 12:00 AM, Darin Fisher<<a href="mailto:darin@chromium.org">darin@chromium.org</a>> wrote:<br>
> I agree. Moreover, since a shared worker identified by a given name cannot<br>
> be "navigated" elsewhere, the name isn't all that synonymous with other<br>
> usages of names (e.g., window.open). At the very least, it would seem<br>
> helpful to scope the name to the URL to avoid the name conflict issue.<br>
> -Darin<br>
<br>
</div>Technically, that can already be done by using the current the current<br>
URL as the name.</blockquote><div><br></div><div>I don't quite understand. Are you suggesting that you can work around this by passing the same parameter twice when creating a shared worker? If so, that seems ugly...and a sign that it should be changed.</div>
</div>