[jdev] Re: Roster caching

Remko Troncon remko at el-tramo.be
Fri May 5 01:44:43 CDT 2006


> I think that's higher complexity. You're attaching a single magic 
> number to the whole roster, and expecting the server to know what 
> needs adding, changing and removing to get to the current version 
> from an arbitrary point in the past.

I don't think that's very hard to compute, given that you store
your deltas in a smart way (cfr. subversion).

This way takes a lot of burden off the client (which is our goal),
and makes it conceptually a lot easier to understand i think.
There is no separation of changes and deletions.

cheers,
Remko



More information about the JDev mailing list