On Thu, Jul 16, 2009 at 3:01 PM, Fabio Forno<[email protected]> wrote: >> They can come from any domain - think of a shared roster/user groups service. > Uhm, I'm trying to think together with presence delivery too. Shared > roster is bit tricky in that, since shared.jabber.org could tell you > that [email protected] is you roster, and then what? If your server > doesn't know that presence is never routed. This seems a special case > where some collaboration with server itself is needed > In all the other cases instead the presence to the service jid is sufficient
Point taken. So even if you're running a shared roster service, it still needs to do JID transformation, and you could well be right :) >> You continue as usua (e.g. for a transport you could have the service >> and the service admin both in your main roster). > I was thinking of removal. If it happens that you have > [email protected] in the main roster and not more in the gateway it > means that you have deleted it, perhaps with a different client, but > you server will still think that you have a subscription. Instead if > we limit the secondary rosters to a subdomain the client know that > missing jids must be deleted from the main roster. (this should happen > in the ideal world, but during the transition it will be the rule) I'm not sure why this one's a big deal - I don't see why the same contact should end up in both your transport roster and your main roster. >>> - do we allow full jids export their own roster to other clients? I'd >>> say no in the case, roster providers can be just domain jids. >> I don't follow - are you asking if e.g. I could share my roster with you? > I was just wondering if a client entity could be a roster provider for > a different client entity. I've no idea of possible applications, and > I'd forbid it, but perhaps it's just lack of "vision" ;) It does sound interesting to be able to see other people's rosters, where authorised, so I wouldn't outright forbid it unless we need to. I have no real use case, though. Best, /K
