On 5/2/2013 7:43 PM, Gregory Szorc wrote:
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.
Will it also be an asynchronous API from the main thread and a
potentially synchronous API from workers?
Transactions already sound like too much API for most clients; perhaps
we need them, but can we also have an optimized API for "store this blob
of data in key 'foo.bar.baz'" ?
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
