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

Massimiliano Mirra iolgzc102 at sneakemail.com
Wed Dec 5 05:36:30 CST 2007

> the next part is not needed. See below.
> > <iq from='server' to='transport' type='get' id='deleg01'>
> >   <query xmlns='roster-delegation'>
> >     <owner jid='client at server'/>
> >   </query>
> > </iq>
> >
> > ...transport logs to legacy service...
> The transport will log on to the legacy service when he receives a
> <presence> stanza. It should be like that to pass along <status> and
> <show> information.

Ah, that's right.

> > Wrapping the roster from the transport rather than overloading its
> > usual function looked attractive, but maybe there are gotchas with one
> > <query> inside another (even if namespaced).
> ENOCRYSTALBALL, can't see reasons for/against either one.

:-)  The "reason for" I see is a purely human one.  No "but roster
queries can also be used to..." for programmers that are learning
about roster management, and less "what does it mean in this context"
for those who are watching a session trace for debugging purposes.


Massimiliano Mirra

More information about the JDev mailing list