[
https://issues.apache.org/jira/browse/VYSPER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503658#comment-13503658
]
Bernd Fondermann commented on VYSPER-333:
-----------------------------------------
Now we're getting to it. Presence Probes.
It's specified here:
http://tools.ietf.org/html/rfc6121#section-4.3
It says that in case of a full JID presence probe only the full JID's presence
is returned, but it also says that if the bare JID is probed, presences for
*all* resources are returned (4.3.2. (4)). So you are right, this looks like a
bug.
Please note:
(a) Presence probes are potentially dangerous with respect to privacy. They
should only be sent to clients with a Directed Presence
(http://tools.ietf.org/html/rfc6121#section-4.6).
(b) The spec says:
>> Presence probes SHOULD NOT be sent by a client, because in general a client
>> will not need to send them since the task of gathering presence from a
>> user's contacts is managed by the user's server.<<
You might run into bandwidth problems when doing a lot of presence probes from
the client side with lots of sessions. Presence stanzas are already a concern
on XMPP servers with a lot of active users (google: "presence storms")
> 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
