[jdev] Roster caching

[Vinod Panicker]

On 5/5/06, Trejkaz <trejkaz at trypticon.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 05/05/2006, at 08:46 AM, Matthias Wimmer wrote:
> > Personally I'd like to implement SyncML on the server which could
> > be used to syncronize all types of data, not just the roster data
> > we are talking about here.
> >
> > SyncML is an XML based syncronization protocol defined by the Open
> > Mobile Alliance (OMA) and already implemented in most modern mobile
> > phones.
>
> Now this is getting interesting.  An XMPP binding for SyncML. :-)
>
> But actually, I think I'd rather have the server push the changes to
> my phone, instead of my phone having to ask for them.  If I know I
> want to keep my contacts in sync, it would be better if changes
> occurred in real-time. ;-)

Agreed that JEP-0150 is limited in terms of functionality.  I do like
Dave's solution, but it would be more complex that JEP-0150.  But it
also does pay dividends.

SyncML is also a possibility for syncing the roster.  Roster pushes
should take care of the real-time roster updates, no?

Clarification needed -
Would such extensions still use the same semantics as specified for
roster retrieval in the RFC?  IMO that would be required, since there
is a state change for the xmpp entity once the roster has been
retrieved.

Regards,
Vinod.