[whatwg] LocalStorage in workers

Drew Wilson atwilson at google.com
Wed Sep 16 15:31:14 PDT 2009


Thanks, Robert - I didn't want to second my own proposal :)
I think that #4 is probably a reasonable bridge API until we come up with a
consensus API for #3. For myself, I see this API as being very useful for
persistent workers (yes, I'm still banging that drum :).

-atw

On Wed, Sep 16, 2009 at 3:21 PM, Robert O'Callahan <robert at ocallahan.org>wrote:

> On Thu, Sep 17, 2009 at 9:56 AM, Jeremy Orlow <jorlow at chromium.org> wrote:
>
>> 1) Create a LocalStorage like API that can only be accessed in an async
>> way via pages (kind of like WebDatabase).
>>
>> 2) Remove any
>> atomicity/consistency guarantees from synchronous LocalStorage access within
>> pages (like IE8 currently does) and add an async interface for when pages do
>> need atomicity/consistency.
>>
>> 3) Come up with a completely different storage API that all the browser
>> vendors are willing to implement that only allows Async access from within
>> pages.  WebSimpleDatabase might be a good starting point for this.
>>
>
> 4) Create WorkerStorage so that shared workers have exclusive, synchronous
> access to their own persistent storage via an API compatible with
> LocalStorage.
>
> This sounds like it has a low implementation cost and solves many use cases
> in a very simple way, right?
>
> Rob
> --
> "He was pierced for our transgressions, he was crushed for our iniquities;
> the punishment that brought us peace was upon him, and by his wounds we are
> healed. We all, like sheep, have gone astray, each of us has turned to his
> own way; and the LORD has laid on him the iniquity of us all." [Isaiah
> 53:5-6]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090916/e80c410f/attachment-0002.htm>


More information about the whatwg mailing list