Software /
code /
prosody-modules
File
mod_storage_multi/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 | 1887:a7fdab9c14e2 |
line wrap: on
line source
--- summary: Multi-backend storage module (WIP) labels: - NeedDocs - Stage-Alpha ... Introduction ============ This module attemtps to provide a storage driver that is really multiple storage drivers. This could be used for storage error tolerance or caching of data in a faster storage driver. Configuration ============= An example: ``` {.lua} storage = "multi" storage_multi_policy = "all" storage_multi = { "memory", "internal", "sql" } ``` Here data would be first read from or written to [mod\_storage\_memory], then internal storage, then SQL storage. For reads, the first successful read will be used. For writes, it depends on the `storage_multi_policy` option. If set to `"all"`, then all storage backends must report success for the write to be considered successful. Other options are `"one"` and `"majority"`.