You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* [MAM] move action related functions to mam_iq
* [MAM] reduce code duplication in mod_mam and mod_mam_muc
Unify message forwarding
* [MAM] export function to build MAM reply
* [MAM] allow to configure call back module for extra lookup params
* [MAM] use exml_query instead of xml
* address PR comments
* Export helpers function from mod_mam_muc
Export a function which handles lookup_messages/2 result and
reponds properly according to MAM version in incoming IQ.
Copy file name to clipboardExpand all lines: doc/modules/mod_mam.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,10 @@ For now `odbc` backend has very limited support for this feature, while `cassand
31
31
***archive_chat_markers** (boolean, default: `false`) - If set to true, XEP-0333 chat markers will be archived. See more details [here](#archiving-chat-markers)
32
32
***pm** (list | `false`, default: `[]`) - Override options for archivization of one-to-one messages. If the value of this option is `false`, one-to-one message archive is disabled.
33
33
***muc** (list | `false`, default: `false`) - Override options for archivization of group chat messages. If the value of this option is `false`, group chat message archive is disabled.
34
+
***extra_lookup_params** (atom, default: `undefined`) - a module implementing `mam_iq` behaviour.
35
+
If this option has value other then undefined, function `extra_lookup_params/2` from this module will be called when building MAM lookup parameters.
36
+
This can be used to extend currently supported MAM query fields by a custom field or fields.
37
+
This field(s) can be added to lookup params later passed to MAM backend.
34
38
35
39
**backend**, **add_archived_element**, **no_stanzaid_element** and **is_archivable_message** will be applied to both `pm` and `muc` (if they are enabled), unless overriden explicitly (see example below).
36
40
@@ -70,9 +74,9 @@ These options will only have effect when the `odbc` backend is used:
70
74
#### Common backend options
71
75
72
76
***user_prefs_store** (atom, default: `false`) - Leaving this option as `false` will prevent users from setting their archiving preferences. It will also increase performance. Other possible values are:
73
-
*`odbc` (ODBC backend only) - User archiving preferences saved in ODBC. Slow and not recommended, but might be used to simplify things and keep everything in ODBC.
74
-
*`cassandra` (Cassandra backend only) - User archiving preferences are saved in Cassandra.
75
-
*`mnesia` (recommended) - User archiving preferences saved in Mnesia and accessed without transactions. Recommended in most deployments, could be overloaded with lots of users updating their preferences at once. There's a small risk of an inconsistent (in a rather harmless way) state of the preferences table.
77
+
*`odbc` (ODBC backend only) - User archiving preferences saved in ODBC. Slow and not recommended, but might be used for simplicity (keeping everything in ODBC).
78
+
*`cassandra` (Cassandra backend only) - User archiving preferences are saved in Cassandra.
79
+
*`mnesia` (recommended) - User archiving preferences saved in Mnesia and accessed without transactions. Recommended in most deployments, could be overloaded with lots of users updating their preferences at once. There's a small risk of an inconsistent (in a rather harmless way) state of the preferences table.
76
80
***full_text_search** (boolean, default: `true`) - Enables full text search in message archive (see *Full Text Search* paragraph). Please note that the full text search is currently only implemented for `odbc` and `riak` backends. Also, full text search works only for messages archived while this option is enabled.
0 commit comments