Description
two issues, which are minor
1. If there is an XMPP message for an incremental refresh, then that refresh will now happen in a separate thread. It was intended to do this before, but it didnt work right. With the 2.6 version, the incremental refresh will still happen without waiting for the full refresh, but it will happen the next time a user clicks a button in the user's thread. For us with a dozen groups, and hundreds of users, it takes several seconds and isnt a big deal
2. If there is an XMPP message for incremental refresh, it clears the cache after some seconds in the future. In the meantime if another action (e.g. add a member in the admin console of atlassian) flushs the cache immediately, it should cancel the cache clear in the background thread. Now that will happen...