4 ms·
Looks interesting, but there doesn’t seem to be any information about what CRDT it’s using, or how it handles concurrent editing at all. The only operation appe
by CGamesPlay 3y ago
Looks interesting, but there doesn’t seem to be any information about what CRDT it’s using, or how it handles concurrent editing at all. The only operation appears to be “set key”, so it looks pretty basic. Is this the target state or is this going to be expanded upon in the future?
- capableweb 3y agohttps://p2panda.org/specification/data-types/documents https://p2panda.org/specification/data-types/documents > A document is made up of operations published by one or many authors > Every operation has a previous field containing a document_view_id which refers to document state at the moment the operation was encoded > DO3: An operation which refers to the current operation in its previous field MUST be sorted next. As far as I understand, it would be up to the client to present potential conflicts and won't be a valid document until it has been resolved.
- andreasdz 3y agoWe're using our own CRDT called "Operations" giving us multi-writer conflict-free editing. It's a simple key/value map with a last-write win rule while we keep some sort of vector clock for every write to understand what every peer has seen when they updated the Document. This might be limiting for some cases, though so far we could model many applications already with such simple CRDT. It is also possible to add your own or already existing CRDT frameworks on top of p2panda.