acid-info
/
vacp2p-rfc
mirror of https://github.com/acid-info/vacp2p-rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

more todos

This commit is contained in:
Oskar Thoren 2019-10-03 11:12:50 +08:00
parent 77ae86a9a8
commit 572f4e5633
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
remote-log.md
View File

@ -126,12 +126,10 @@ message RemoteLog {
<!-- TODO: Better name for Pair, Mapping? --> <!-- TODO: Better name for Pair, Mapping? -->
<!-- TODO: Extend pair with (optional) data --> <!-- TODO: Consider making more useful in conjunction with metadata field. It makes sense to explicitly list what sequence a message is <local hash, remote hash, data, seqid> this way I can easily sync a messages prior or after a specific number. To enable this to be dynamic it might make sense to add page info so that I am aware which page I can find seqid on -->
## Synchronization ## Synchronization
<!-- TODO: Elaborate on interaction with MVDS, especially with what messages are synced, etc -->
### Roles ### Roles
There are four fundamental roles: There are four fundamental roles:
@ -145,6 +143,9 @@ The *remote log* protobuf is what is stored in the name system.
"Bob" can represent anything from 0 to N participants. Unlike Alice, Bob only needs read-only access to NS and CAS. "Bob" can represent anything from 0 to N participants. Unlike Alice, Bob only needs read-only access to NS and CAS.
<!-- TODO: Document random node as remote log -->
<!-- TODO: Document how to find initial remote log (e.g. per sync contexts -->
### Flow ### Flow
<!-- diagram --> <!-- diagram -->
@ -204,8 +205,6 @@ semantics, this gives users flexibility in terms of bandwidth and
latency/indirection, all the way from a simple linked list to a fully replicated latency/indirection, all the way from a simple linked list to a fully replicated
log. The latter is useful for things like backups on durable storage. log. The latter is useful for things like backups on durable storage.
<!-- TODO: Consider making more useful in conjunction with metadata field. It makes sense to explicitly list what sequence a message is <local hash, remote hash, data, seqid> this way I can easily sync a messages prior or after a specific number. To enable this to be dynamic it might make sense to add page info so that I am aware which page I can find seqid on -->
### Next page semantics ### Next page semantics
The pointer to the 'next page' is another remote log entry, at a previous point The pointer to the 'next page' is another remote log entry, at a previous point
@ -213,6 +212,8 @@ in time.
<!-- TODO: Determine requirement re overlapping, adjacent, and/or missing entries --> <!-- TODO: Determine requirement re overlapping, adjacent, and/or missing entries -->
<!-- TODO: Document message ordering append only requirements -->
### Interaction with MVDS ### Interaction with MVDS
[vac.mvds.Message](./mvds.md#payloads) payloads are the only payloads that MUST be uploaded. Other messages types MAY be uploaded, depending on the implementation. [vac.mvds.Message](./mvds.md#payloads) payloads are the only payloads that MUST be uploaded. Other messages types MAY be uploaded, depending on the implementation.