Why the binded resource change when client trying to perform stream resumption? (XEP-0198)
We're using Tigase 5.2.0 and we found a problem in stream resumption. The situation is like this:
There are 2 mobile clients, lets say A and B.
A keep sending message to B
B switch to airplane mode and A keep sending message
B goes online again and try to perform stream resumption
We found that when B goes online and try to perform stream resumption, it failed. Upon further checking, the resource of user_b has changed, it is assigned with "tigase-x" where x is a random number, it is no longer binded to resource 'MyResource', although we set it explicitly with 'MyResource'. Then resumption failed with "unexpected-request", all the messages sent by A will then go to offline message after resumption timeout. B will retrieve them after logout and login. (Message are now out of order)
However, we found that if A did not send message to B before it goes online again, resumption works and resource not changed.
Any comments would be appreciated. :)