[standards-jig] gateway handling of legacy contact lists
JHildebrand at jabber.com
Sat Dec 13 01:01:32 UTC 2003
What if I log in with Y!, add someone to my roster, and then log back in
through the gateway?
I think the gateway has to keep state as to which users it has sent
x:rosters for. When it retrieves the remote roster on login, it should
compare the two, and send an x:roster with new contacts (and unsubscribed
for ones that aren't there any more).
> -----Original Message-----
> From: Peter Millard [mailto:me at pgmillard.com]
> Sent: Friday, December 12, 2003 4:19 PM
> To: standards-jig at jabber.org
> Subject: Re: [standards-jig] gateway handling of legacy contact lists
> Paul Curtis wrote:
> > Yes, and this is a problem. When I send the roster a second
> time when
> > the user logs into Yahoo, and the group is set, the user gets two
> > entries in their roster. Without getting the roster and reading it,
> > how do you propose to solve this? If I send the jabber:x:roster
> > without a group, then the user can move them around without having
> > duplicates appear in their roster.
> I don't follow.. The yahoo-t should only send me a message w/
> the roster when I sucessfully REGISTER (not login) w/ the
> transport. And the client should be smart enough to not show
> the entries which are already on that user's jabber roster
> (searching by jid).
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards