+1
On Jun 6, 2008, at 2:05 PM, Peter Saint-Andre wrote:
RFC 3921 states that the server shall send subscription requests and
roster pushes to a resource only if the resource has both (a) sent
available presence and (b) requested the roster. In rfc3921bis, a
resource that has done both of these is called an "interested
resource".
Some time ago we discussed the idea of specifying that:
1. The server shall send subscription requests if the resource has
sent
available presence.
2. The server shall send roster pushes if the resource has requested
the
roster.
3. We will not condition sending subscription requests on the action
of
requesting the roster, and we will not condition sending roster pushes
on the action of sending available presence.
Traditionally (going back to the early jabberd releases), rosters and
presence subscriptions have been closely conjoined -- thus the concept
of an interested resource. I have not thought through the implications
of changing that, but it does seem cleaner to tie roster pushes only
to
requesting the roster and to tie presence subscriptions only to
sending
available presence.
Feedback is welcome on this topic before I make any changes to
rfc3921bis.
Peter
--
Peter Saint-Andre
https://stpeter.im/
