New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Approach to message size is not consistent in clone protocol #85

Open

gsvarovsky opened this issue Jan 30, 2022 · 0 comments

Labels

Member

gsvarovsky commented Jan 30, 2022 •

edited

Loading

In the transport-independent clone-clone interface (see TS interface in JS engine)

Individual published operations are of (potentially) restricted size and are modelled as one "message"
Recovery operations are of arbitrary size (may be fused) and are modelled as one message
Snapshots are also of arbitrary size (usually, but not necessarily, bigger), but are modelled as a stream

The protocol could be more abstract and treat a snapshot as one coherent message, or all messages as streams.

(Arose in consideration of proximate causes to an agreement, see security project design)

gsvarovsky added the investigate label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment