utility crate: Indexed DB about gloo HOT 6 OPEN

I'm experimenting with a high level indexed db wrapper (futures based) here. Feedback is welcome. 😁

from gloo.

It should also fully support Futures, since all the IndexedDB APIs are asynchronous.

from gloo.

high level semantics

I agree that we want to get there, but I am a big fan of creating layers that go from raw -sys style bindings up to callbacks, then to futures, and finally to a high level semantics along the way. This allows folks to reuse whichever layer is appropriate if they are building an alternative style of high level API or if they need direct bindings access, etc.

from gloo.

Absolutely in agreement. Just wanted to clarify on what layers are being set as expectations in the scope of gloo and what's built outside of it.

from gloo.

I think approaching with a similar high level semantics, like Dexie in JS, would probably be the key in making it actually usable. Indexed DB is tedious to use as it is, and I'm afraid of even thinking about a Rust-y future chaining for low level request, responses and error handling of IndexedDB.

from gloo.

See also the discussion happening in #27 about layers of APIs.

from gloo.