vladris / fluid-ledger Goto Github PK

That's when this client owns the document. Once attached, snapshot happens and other clients load from snapshot. Behavior should be to immediately apply appends and fire event during detached state.

Stashed ops happen when disconnected, applyStashedOp is invoked on reconnect. We likely can't support offline with this DDS as sequencing is important.

These could potentially be different flavors of the DDS with additional functionality:

• Provide a clear op to clear the list/reset. In case full history is not important.
• Currently ledger grows unbounded. We could potentially have configurable N and M such that when ledger reaches N items, we delete (shift) the first M items and fire an event for clients to handle. We lose the full history but we gain infinite append.
• Context-dependent append: client might chose to append an item based on its known state of the world (local ledger). If another client interleaves an append, so when our append gets sequenced, ledger is different, we can fire a different event (rejected) and let client decide whether to resubmit. Other clients would ignore the op. We should be able to easily implement this by including ledger length when we submit the op and checking against actual length when we get the op back (note previous 2 ideas might shorten ledger, in which case we can keep a separate counter for the length).