Add support for fetching configured and maximal retention period (#82)

Andrzej Wójcik (Tigase) opened 12 months ago

Add support for fetching configured and maximal retention period

Andrzej Wójcik (Tigase) added "Related" Customers/atom#38 12 months ago
Andrzej Wójcik (Tigase) added "Related" tigase/_server/server-core#1537 12 months ago
Andrzej Wójcik (Tigase) changed state to 'In Progress' 12 months ago
Previous Value Current Value
Open

In Progress
Andrzej Wójcik (Tigase) commented 12 months ago

I've implemented ad-hoc command at user bare JID on node urn:xmpp:mam#configure. This command will have a field with name (var) set to retentionInDays and value of this field will be set to the message retention time in days.

If option is user configurable, field will be of type text-single and submittion of a new form with a new value will change retention time . If the value is enforced by the installation, then this field will be of type fixed.

To make it fully work as expected, MAM component requires configuration for removing expired messages.
Andrzej Wójcik (Tigase) changed state to 'In QA' 12 months ago
Previous Value Current Value
In Progress

In QA
Wojciech Kapcia (Tigase) commented 7 months ago

There was a tiny bug in MAM VHostExtension preventing configuration of the Number of days and always falling back to UserDefined which was reflected in the ad-hoc returned result.
Login to comment

Previous Value	Current Value
Open	In Progress

Previous Value	Current Value
In Progress	In QA

Iterations

Issue Votes (0)

Watchers (3)

Reference

tigase/_server/tigase-message-archiving#82