Discussion History Management not Honored (#19)

Glenn Engstrand opened 1 decade ago

When joining a MUC, the clients sends a http://xmpp.org/extensions/xep-0045.html#enter-managehistory compliant presence packet like this.

2011-10-02 19:26:20 BoshConnectionManager.processSocketData() FINEST: Processing socket data: from=null, to=null, DATA=, SIZE=360, XMLNS=http://jabber.org/protocol/httpbind, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=null

Yet the entire message history (up to the last restart of Tigase) of the chat room gets sent back to the client.

Activities

Volodymyr Iatsyshyn commented 1 decade ago

Added implementation of 7.1.16 Managing Discussion History and tests for it

Note: all invalid values of attributes are ignored.

Tried adding scripted test 'history.cor', but XMPPTestCase.test() do not catch messages that are send via delayDeliveryThread.put()
Bartosz Małkowski commented 1 decade ago

Fixed in another case.
Login to comment

Type	Bug
Priority	Normal
Assignee	Glenn Engstrand
RedmineID	270

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-muc#19