RSM sends <max/> element in response (#27)

Closed

Activities

Andrzej Wójcik (Tigase) opened 5 months ago

As reported in our support channel:

the XEP-0059 implementation will return <max/> in the RSM result <set/> element, which is at least nothing the standard says you should or shouldn't do

As this value is mostly unused and client can know the value of <max/> by counting received items, this element in RSM returned by Tigase is redundant and can be removed.

Referenced from commit 5 months ago

Removed <max/> from RSM response #27

Andrzej Wójcik (Tigase) committed 5 months ago

35bbed6a

Andrzej Wójcik (Tigase) changed state to 'In Progress' 5 months ago

Previous Value	Current Value
Open	In Progress

Andrzej Wójcik (Tigase) changed state to 'In QA' 5 months ago

Previous Value	Current Value
In Progress	In QA

Andrzej Wójcik (Tigase) commented 5 months ago

<max/> element was removed from RSM responses.

wojciech.kapcia@tigase.net added to iteration "tigase-server-8.4.0" 4 months ago

wojciech.kapcia@tigase.net changed fields 4 months ago

Name	Previous Value	Current Value
Version	empty	tigase-server-8.4.0

Andrzej Wójcik (Tigase) changed state to 'Closed' 4 months ago

Previous Value	Current Value
In QA	Closed

Type	Task
Priority	Normal
Assignee	Andrzej Wójcik (Tigase)
Version	tigase-server-8.4.0
Target Release	1.1
Sprints	n/a
Customer	n/a

Iterations

tigase-server-8.4.0 Closed

Issue Votes (0)

Watchers (3)

Reference

tigase/_server/tigase-utils#27