I don't quite get the idea.
It would be cool to draft an API for leveldb with
- `thing.get(key)`
- `thing.batchUpdate(changes)`
- `thing.rangeQuery(start, end)`
If we can cover concurrent updates & reads as well as concurrent streaming reads that should cover all bases.
I like the idea of giving it a set of automatons but I can't imagine how that would work.
I want to prototype an API for this (in JS). The other concern of course is errors, all three of those operations can return either a result / void or an error.
Also the `rangeQuery()` will have a notion of end that we need to capture. Your current websocket API (
https://github.com/evancz/Elm/blob/dev/libraries/Native/Signal/WebSocket.js#L12 ) does not capture the notion of close.
The notion of close is very important to handle network disconnections for mobile apps.