View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010082 | Taler | specification | public | 2025-06-05 16:24 | 2025-06-05 19:51 |
| Reporter | avalos | Assigned To | |||
| Priority | normal | Severity | text | Reproducibility | have not tried |
| Status | confirmed | Resolution | open | ||
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0010082: design document for (CRDT) incremental sync protocol | ||||
| Description | The new sync protocol with CRDT functionality should be discussed and specified in detail, including: - What should be backed up (and what not)? - When should backups run (and when not)? - When to backup/restore incrementally (and when not)? - Encoding of changes/deletions and other events. - Garbage collection and DB maintenance. - Client-side conflict resolution. - Complementary data structures (i.e. blob hash table). - etc, etc, etc. | ||||
| Tags | vivy | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-05 16:24 | avalos | New Issue | |
| 2025-06-05 16:24 | avalos | Tag Attached: vivy | |
| 2025-06-05 19:51 | Christian Grothoff | Severity | minor => text |
| 2025-06-05 19:51 | Christian Grothoff | Status | new => confirmed |
| 2025-06-05 19:51 | Christian Grothoff | Product Version | => git (master) |
| 2025-06-05 19:51 | Christian Grothoff | Target Version | => post-1.0 |
