[
https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500915#comment-13500915
]
Bernd Fondermann commented on VYSPER-333:
-----------------------------------------
Again, in XMPP, the last set status is the latest, regardless of the resource.
So, as far as Vysper and XMPP is concerned, everything is working correctly -
although it's causing troubles in your application.
You could think about using Directed Presence (see XMPP RFCs) or work with
per-client priorities, if you can identify a "leading" client.
Or, as I already said, use different accounts.
> presence message should bring the resource information of one user;
> -------------------------------------------------------------------
>
> Key: VYSPER-333
> URL: https://issues.apache.org/jira/browse/VYSPER-333
> Project: VYSPER
> Issue Type: Bug
> Components: stanza routing
> Affects Versions: 0.7
> Environment: normal environment;
> Reporter: wan jian ming
>
> when one on logins, he/she will get the presence information from all of its
> rosters. but in the presence message there are no resource jid, so the client
> don't know exactly how many logins there.
> for example A has a friend B. but before A is login. there are two logins of
> B already. so when A got prenence message of B, it only get two B@*** ,
> without resource in the JID; so when B logout, the client of A can't show the
> status correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
