3 ms·
There is currently no "disconnect-and-set" functionality, but it's on the roadmap and will happen soon. It just didn't land into v1. Since Horizon is backed by
by coffeemug 10y ago
There is currently no "disconnect-and-set" functionality, but it's on the roadmap and will happen soon. It just didn't land into v1.
Since Horizon is backed by RethinkDB, it's transaction properties are the same as that of RethinkDB. Check out this document for the specifics -- http://rethinkdb.com/docs/consistency/ http://rethinkdb.com/docs/consistency/.
- akanet 10y agoThanks for that. Can you clarify disconnect behavior in general? Do subscribed changesets resume if your internet blips? Also, there doesn't seem to be a callback arg in Collection#store: http://horizon.io/api/collection/#store http://horizon.io/api/collection/#store. This is worrying. How do I know if a write succeeded? Edit: found http://horizon.io/api/collection/#subscribe http://horizon.io/api/collection/#subscribe - you chain subscribe to writes when you care about their success