File

mod_storage_appendmap/README.markdown @ 4515:2e33eeafe962

mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parent 2818:88474dd1af48
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
- 'Type-Storage'
summary: Experimental map store optimized for small incremental changes
...

This is an experimental storage driver where changed data is appended.
Data is simply written as `key = value` pairs to the end of the file.
This allows changes to individual keys to be written without needing to
write out the entire object again, but reads would grow gradually larger
as it still needs to read old overwritten keys. This may be suitable for
e.g. rosters where individual contacts are changed at a time. In theory,
this could also allow rolling back changes.

Requires 0.10