2010/9/8 Dave Cridland <[email protected]>: >> The solution would be that the server sends AAA the entire roster in >> step 4, but based on what? > > You'd store a roster as: > > <query xmlns='jabber:iq:roster' x237:xmlns='xep-0237-extra-data' > x237:lastdeleted='0'> > <item jid='[email protected]' x237:changed='11'/> > <item jid='[email protected]' x237:changed=14'/> > </query> > > Then when bob's deleted, you do: > > <query xmlns='jabber:iq:roster' x237:xmlns='xep-0237-extra-data' > x237:lastdeleted='15'> > <item jid='[email protected]' x237:changed=14'/> > </query> > > Now in step 4, client='14', so you send the complete roster because > lastdeleted > client. > > Obviously if, given the original roster, a client asks for 12, then > lastdeleted <= client, and therefore you send an empty result, and then push > any items where changed > client (if any).
Ok, I get the point :) Thanks a lot to all. -- Iñaki Baz Castillo <[email protected]>
