[jdev] XEP-0100 and roster/legacy contact list sync

[Magnus Henoch]

"Massimiliano Mirra" <iolgzc102 at sneakemail.com> writes:

> Thanks, Magnus.  I guess that would be straightforward for an internal
> server component, which has access to the user's roster.  Any idea
> about how an external component might do the same without caching the
> contact list?  (I don't see how that would be possible, but it
> wouldn't be the first time I miss the obvious.)

A random idea: if the legacy server provides some kind of versioning of
the contact list (ICQ does), the transport could save just the last
version/date that was synced to the Jabber roster.  If there's a newer
version on the legacy service, the transport can just send "subscribe"
stanzas for _all_ contacts; the user's server will weed out the ones
that already have subscription (section 5.1.6 of RFC 3921).

-- 
Magnus
JID: legoscia at jabber.cd.chalmers.se