On Thu, Jul 16, 2009 at 9:49 AM, Pedro Melo<[email protected]> wrote: > > > I've been thinking about this problem and I don't see a solution for this > that is compatible with different generation of clients (those who support > trusted sources for jabber:iq:roster and those that don't). > > I think this might be one situation where you would have to use a big bang > approach: each user decides which protocol he wants to use, and all his > clients must use that one. > > I'm hoping someone smarter will come up with something better though :) > > Best regards,
I've been thinking about it too. Indeed which is the real problem? Just duplicated entries, which will be seen by the new client only, and we can cope with them while merging the rosters and giving precedence to the component's entries. The benefits are so high that we can live with this little issue ;) bye -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: [email protected]
