[
https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-333:
------------------------------------
Component/s: (was: stanza routing)
core protocol
Description:
presence probes are not properly handled. (
http://tools.ietf.org/html/rfc6121#section-4.3 )
As long as only one resource is active, everything looks fine.
But if more than one resource is active for a session, this should apply:
1. If presence probe is for the bare JID, *all* resource's presences should be
returned.
2. If presence probe is for a full JID, *only that* resource's presence should
be returned.
was:
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.
Summary: Presence probes not properly handled for multiple sessions
(was: presence message should bring the resource information of one user;)
> Presence probes not properly handled for multiple sessions
> ----------------------------------------------------------
>
> Key: VYSPER-333
> URL: https://issues.apache.org/jira/browse/VYSPER-333
> Project: VYSPER
> Issue Type: Bug
> Components: core protocol
> Affects Versions: 0.7
> Environment: normal environment;
> Reporter: wan jian ming
>
> presence probes are not properly handled. (
> http://tools.ietf.org/html/rfc6121#section-4.3 )
> As long as only one resource is active, everything looks fine.
> But if more than one resource is active for a session, this should apply:
> 1. If presence probe is for the bare JID, *all* resource's presences should
> be returned.
> 2. If presence probe is for a full JID, *only that* resource's presence
> should be returned.
--
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
