- From: Jeremy Orlow <jorlow@chromium.org>
- Date: Wed, 16 Sep 2009 15:30:21 -0700
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. > Ah yes. That is also an option. And, now that I think about it (combined with Jonas' last point) I think it might be the best option since it has a very low implementation cost, it keeps the very simple API, and solves the primary problem of not blocking pages' event loops. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090916/8f4d9bf9/attachment.htm>
Received on Wednesday, 16 September 2009 15:30:21 UTC