On Tue, Jul 14, 2009 at 8:11 PM, Peter Saint-Andre<[email protected]> wrote: > We have long resisted this because we saw jabber:iq:roster as all and > only between you and your server (cf. recent discussion about 3921bis on > the XMPP WG list). If we remove that restriction, you can have a "roster > relationship" with any other entity, such as shared groups service.
With the only caveat that clients must pay attention to the from in roster sets. This puts a bit more complexity in the service and the client, especially if we want to support roster versioning for all the components, but the overall advantages are clear. I like it also for social applications, in that way the service can add/remove special contacts accordingly to the active feeds of the user, without cluttering the main roster >> So yes, let's use standard rosters for transports and shared groups, >> and let's keep roster item exchange just for sharing contacts. > > WFM. Two small issues: - it won't work until servers route the packets (small fix, but upgrades are needed) - transition will be difficult, since if it can't work while using two different clients of which just one supports it (and the case is very common, since nobody uses the same client for teh desktop or mobiles) -- Fabio Forno, Ph.D. Ooros srl jabber id: [email protected]
