<br><br><div class="gmail_quote">On Mon, Oct 12, 2009 at 19:07, Ian Hickson <span dir="ltr"><<a href="mailto:ian@hixie.ch">ian@hixie.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>[SNIP]<br>
On Wed, 23 Sep 2009, Brett Cannon wrote:<br>
><br>
> Before the move to structured clones one could tell if a key was set by<br>
> calling getItem() and seeing if it returned null (had to use === as<br>
> someone could have called setItem() w/ null, but that would be coerced<br>
> to a string for storage). But with the latest draft's switch to<br>
> structured clones that test no longer clearly differentiates between<br>
> whether the value returned by getItem() signifies that the key was not<br>
> set, or the key was set with the value null.<br>
<br>
I believe you can test if a key is in the storage area using:<br>
<br>
if (key in storage) { ... }<br>
<br>
For example:<br>
<br>
if ('document' in window.localStorage) { ... }<br>
<br></blockquote><div><br></div><div>I didn't find that in the spec anywhere. Is it somehow implicit and I just missed it? Or will it be specified sometime in the future?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
> And since I just subscribed to the mailing list, I was wondering if the<br>
> whole workers/localStorage discussion ended or not, as I can provide a<br>
> (potentially minor) real-world use-case for sharing access between the<br>
> page and worker if people want to hear it (in a new email of course).<br>
<br>
I think everyone agrees that we need a storage mechanism in workers; the<br>
question is what it should be. That's basically the same as the question<br>
of what should happen with the Web Database spec -- I don't think we would<br>
want to end up with multiple storage systems in workers. The answer to<br>
this question depends on the result of this debate in the Web Apps WG.<br>
<br></blockquote><div><br></div><div>Since I am not a w3c member and thus cannot subscribe to the Web Apps WG mailing list, just want to say good luck to whomever pushes this. I truly hope you guys can agree on a single storage solution that the browsers all implement. It would definitely help keep my PhD thesis relevant after it's finished. =)</div>
<div><br></div><div>-Brett</div></div>