|
Andrzej Wójcik (Tigase) opened 5 years ago
|
||||||
|
Wojciech Kapcia (Tigase) batch edited 11 months ago
|
||||||
|
|
Moving MAM directly into core-server and integrating support for Message Offline Storage would significantly improve and simplify processing: messages would be stored into archive/repository faster without the need to pass them to external component. What's more - basing offline store on it will remove data duplication and offline message handling. The idea being to have single table for messages - both MAM and Offline store. With MAM enabled offline store messages would be flagged as delivered (or removed if MAM would be disabled) (accepted in |
||||||
|
|
Wojciech Kapcia (Tigase) added to iteration "tigase-server-9.0.0" 4 days ago
|
||||||
|
|
Wojciech Kapcia (Tigase) removed from iteration "Candidate for next major release" 4 days ago
|
| Type |
Task
|
| Priority |
Normal
|
| Assignee | |
| Version |
Candidate for next major release
|
Iterations
-
tigase-server-9.0.0 Open
Issue Votes (0)
Watchers (2)
It would be good to move the storage of offline messages to the MAM archive if it is available. This way a message would be stored only once (not twice) and we would have a single archive for messages.