[jdev] Possible inconsistency with roster pushes

Vinod Panicker vinod.p at gmail.com
Fri Oct 26 02:02:26 CDT 2007


According to the current RFC and the bis version, roster pushes are to
be sent to "available" resources that have requested the roster only.
I think it makes more sense to say that roster pushes should be sent
to "active" resources that have requested the roster.

For instance, there would be a scenario wherein an automated client
would be doing roster management without the need to have presence.
It would require to be updated on roster activities without the need
for presence information about contacts.

Another case is when a client representing a user resource "a"
switches from available to active state and another resource "b" adds
a presence subscription to contact "c".  The server will not send a
roster push to "a" since its not "available".  "a" subsequently comes
online and the presence information of "c" is received by "a", but the
client does not process it since it is not aware of the roster item.



More information about the JDev mailing list