KyotoCabinet might make a good backend for a new storage API: http://fallabs.com/kyotocabinet/
There is also a companion indexing engine: http://fallabs.com/kyototycoon/ Regards, David ----- Original Message ----- From: "Gregory Szorc" <g...@mozilla.com> To: "Kyle Huey" <m...@kylehuey.com> Cc: "Taras Glek" <tg...@mozilla.com>, "David Rajchenbach-Teller" <dtel...@mozilla.com>, "dev-platform" <dev-platform@lists.mozilla.org>, "Lawrence Mandel" <lman...@mozilla.com> Sent: Thursday, May 2, 2013 6:43:14 PM Subject: Re: Storage in Gecko On 5/2/2013 4:40 PM, Kyle Huey wrote: > > > On Thu, May 2, 2013 at 4:36 PM, Gregory Szorc <g...@mozilla.com > <mailto:g...@mozilla.com>> wrote: > > We seemed to converge on a (presumably C++-based) storage service > that has named branches/buckets with specific consistency, > flushing, etc guarantees. Clients would obtain a handle on a > "branch," and perform basic I/O operations, including > transactions. Branches could be created ad-hoc at run-time. So > add-ons could obtain their own storage namespace with the storage > guarantees of their choosing. Under the hood storage would be > isolated so failures in one component wouldn't affect everybody. > > > So this is basically prefs on steroids? Sure. I'd say it's key-value storage done right with a sane API and consistency expectations and without the association with "preferences"/about:config. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
