JC Brand 789654d54e Updates #785 and #787 ... Improve upon the previous implementation. If the resource with the highest priority goes offline or becomes unavailable, then the chat status of the contact must fall back to that of the resource with the next highest priority. In your example from #785, if the resource with priority 1 goes offline or becomes unavailable, then in your implementation the chat status would stay at online, although it must actually go to xa. The solution is to update the resources attribute on the contact to not just be an array or strings, but instead to be a map of resources to priorities and statuses and to use that data structure.		2017-02-20 22:29:13 +01:00
..
source	Make keepalive and roster_groups true by default.	2017-02-17 08:54:58 +01:00
.gitattributes	Merge branch 'master' into amd-strophe	2015-02-22 12:53:18 +01:00
API.rst	Document the API methods we'll need. Updates #46, Updates #87	2013-11-24 16:23:37 +02:00
CHANGES.md	Updates #785 and #787	2017-02-20 22:29:13 +01:00
DEVELOPER.rst	Bugfix. Handle case where user accepts request.	2014-07-23 19:11:29 +02:00
LICENSE.txt	Update contributors text, readme and add new license (MPL)	2014-03-22 02:11:34 +02:00
RELEASE_CHECKLIST.txt	Remove unused parts from Gruntfile	2015-10-27 09:11:36 +00:00