https://github.com/WebReflection/db
This also solves clashing problems, using a name for the db. This is an
issue to address ASAP in any new db thingy, IMO. Thanks for consideration.
Br
Sent from my Windows Phone
------------------------------
From: Andrea Giammarchi <andrea.giammarchi@gmail.com>
Sent: 2/14/2014 15:28
To: Tobie Langel <tobie.langel@gmail.com>
Cc: public-nextweb@w3.org
Subject: RE: DOM NamedStorage Interface Proposal
I use localForage since 3 years or more via db, a project of mine in
githib, but this has nothing to do with async, rather with libraries
clashing, no matter if sync or not. You know what I mean?
Sent from my Windows Phone
------------------------------
From: Tobie Langel <tobie.langel@gmail.com>
Sent: 2/14/2014 15:05
To: Andrea Giammarchi <andrea.giammarchi@gmail.com>
Cc: public-nextweb@w3.org
Subject: Re: DOM NamedStorage Interface Proposal
There's a lot more value in defining an async store (à la localForage[1])
and making sure it doesn't sport these kind of issues than in proposing
fixes to a sync store vendors no longer want to spend resources on.
--tobie
[1]: http://mozilla.github.io/localForage/
On Feb 14, 2014, at 23:07, Andrea Giammarchi <andrea.giammarchi@gmail.com>
wrote:
oh dear .. the link ...
https://gist.github.com/WebReflection/9010248#dom-namedstorage-interface-proposal
On Fri, Feb 14, 2014 at 2:07 PM, Andrea Giammarchi <
andrea.giammarchi@gmail.com> wrote:
> I rather link directly the gist and patiently wait for comments,
> suggestions, or any sort of thoughts about this.
>
> Thanks and Best Regards,
> Andrea Giammarchi
>