1786
|
1 |
#summary XEP-0136: Message Archiving frontend for mod_mam |
|
2 |
#labels Stage-Alpha |
|
3 |
|
|
4 |
= Introduction = |
|
5 |
|
|
6 |
Implementation of [http://xmpp.org/extensions/xep-0136.html XEP-0136: Message Archiving] for [mod_mam]. |
|
7 |
|
|
8 |
|
|
9 |
= Details = |
|
10 |
|
|
11 |
See [mod_mam] for details. |
|
12 |
|
|
13 |
= Usage = |
|
14 |
|
|
15 |
First configure mod_mam as specified in it's [mod_mam wiki]. Make sure it uses sql2 storage backend. |
|
16 |
|
|
17 |
Then add "mam_archive" to your modules_enabled list: |
|
18 |
{{{ |
|
19 |
modules_enabled = { |
|
20 |
-- ... |
|
21 |
"mam_archive", |
|
22 |
-- ... |
|
23 |
} |
|
24 |
}}} |
|
25 |
|
|
26 |
= Configuration = |
|
27 |
|
|
28 |
Because of the fact that [http://xmpp.org/extensions/xep-0136.html XEP-0136] defines a 'conversation' concept not present in [http://xmpp.org/extensions/xep-0313.html XEP-0313], we have to assume some periods of chat history as 'conversations'. |
|
29 |
|
|
30 |
Conversation interval defaults to one day, to provide for a convenient usage. |
|
31 |
|
|
32 |
{{{ |
|
33 |
archive_conversation_interval = 86400; -- defined in seconds. One day by default |
|
34 |
}}} |
|
35 |
|
|
36 |
That is the only reason SQL database is required as well. |
|
37 |
|
|
38 |
= Compatibility = |
|
39 |
|| 0.10 || Works || |
|
40 |
|| 0.9 || Does not work || |
|
41 |
|
|
42 |
|| PostgreSQL || Tested || |
|
43 |
|| MySQL || Not tested || |
|
44 |
|| SQLite || Tested || |