[
https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500858#comment-13500858
]
Bernd Fondermann edited comment on VYSPER-333 at 11/20/12 6:20 AM:
-------------------------------------------------------------------
This isn't a bug - it's by design of XMPP. Only the last, latest presence for
an account is the current one, from whatever resource it comes. To achieve what
you are describing you would need users to use one account per device (but in
the regular chat scenario with arbitrary remote users, you can't force that).
was (Author: brainlounge):
This isn't a bug - it's by design of XMPP. Only the last, latest presence
is the current one. To achieve what you are describing you would need users to
use one account per device (but in the regular chat scenario with arbitrary
remote users, you can't force that).
> 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
