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

Andrzej Wójcik (Tigase) opened 2 years 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.

Activities

Andrzej Wójcik (Tigase) changed state to 'In Progress' 2 years ago
Previous Value Current Value
Open

In Progress
Andrzej Wójcik (Tigase) changed state to 'In QA' 2 years ago
Previous Value Current Value
In Progress

In QA
Andrzej Wójcik (Tigase) commented 2 years ago

<max/> element was removed from RSM responses.
Wojciech Kapcia (Tigase) added to iteration "tigase-server-8.4.0" 1 year ago
Wojciech Kapcia (Tigase) changed fields 1 year ago
Name Previous Value Current Value
Version
empty
tigase-server-8.4.0
Andrzej Wójcik (Tigase) changed state to 'Closed' 1 year ago
Previous Value Current Value
In QA

Closed
Login to comment

Previous Value	Current Value
Open	In Progress

Previous Value	Current Value
In Progress	In QA

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

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