currently I am stumbling with this warning from Smack, where our Server bulk-pushes an entire roster update.
While I agree, that smack is right here, according to this thread
and the mentioned RFC, it leaves me with the problem, that I can not even receive a callback, that this just happened, so I could react with a “roster.reload()” call or something similar.
In case, you have not really a control over the server implementation and the server works with lots of “virtual” rosters, which can be swapped entirely by setting some values in the server web-ui … how could I approach a solution here?
What is a virtual roster?
The server is a cloud based telephony system controlling many companies and you can set, what (or better: whom) you want to see by setting filters over all the people on the server, like “company grouped”, “my groups”, and the like, depending on your permissions and allowed settings.
This causes an entire roster to be published to you.
This is not a system where “subscriptions” are made, where “buddies” (in the form of subscribe/accept) are done between two explicit users (at least, this is not the normal case). It’s more like a view over the people and the server handles all that stuff for you.
Maybe I missed some interface/listener/callback where I can react on that warning so I can issue a roster.reload() call when this happens?
Any hints for me?
Thanks in advance, Cheers