Andrzej Wójcik (Tigase) opened 5 years ago
-
Wojciech Kapcia (Tigase) batch edited 1 year ago
Name Previous Value Current Value Iterations
empty Candidate for next major release
-
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
Message-Id: <B35F60E5-7C86-4CD6-8B2B-FF7EDF755DFF@tigase.net>onDate: Wed, 23 Apr 2025 15:59:41 +0000 (UTC)) -
-
| 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.