A couple of additional suggestions

Stuart K. Bingë list at codefusion.co.za
Mon Aug 16 15:38:03 CEST 2004

On Monday, 16 August 2004 15:18, Martin Konold wrote:
> > between interchanged messages. It also allows one to see how many times a
> > specific object has been updated over its lifetime, which doesn't hurt to
> > have.
> Please be aware of the fact that this will not work reliably with
> disconnected clients.
> Note: The imap store is _not_ a db!

How exactly is this currently handled, i.e. what happens when a disconnected 
client syncs, modifies an object, tries to sync again, and realises that the 
object was modified by another client between the two syncs?

I would think it should cancel the object edit/save, reload the (new) modified 
object, perhaps update the fields that were previously modified by the user 
before syncing (i.e. merge the newly loaded object and the user-edited 
object), and then resave after a user confirmation.

In this case the revision tag can work reliably. Unless this scenario that I 
described is totally off...

There's a problem if the edited object no longer exists at the second sync, 
however. How is this case currently handled?

Stuart Bingë
Code Fusion cc.

Office: +27 11 673 0411
Mobile: +27 83 298 9727
Email: s.binge at codefusion.co.za

Tailored email solutions; Kolab specialists.

More information about the format mailing list