Hi,
We had a conf call this afternoon on this subject and touched a number
of subjects. Here are my simplified note. People in the call, please add
whatever significant we discussed (create new threads so that we don't
mix everything). In the action list, we already decided of a couple of
threads to start (see below).
Cheers,
- Philippe
------------
Present: Morgen, Brian, Mimi, Philippe, Jeffrey, Katie
Issue: Stamping workflow (based on Brian's scenario)
Will email be able to do the same kind of merge than sharing? Yes if we
can send the XML/EIM description. Brian proposing we leverage that work
so that email update and sharing use as much as the same logic as possible.
Concept of sequence number: this will help identify conflicts. Proposed
by Jeffrey.
Can we use the time of change? There's no sure centralized time stamping
system for emails (no guarantee that time is accurate). See for instance
your email client where emails can sometimes show out of sequence in a
thread.
We think that, despite the possible conflicts resolutions (namely:
conflicts being solved differently by different machines because of the
different order things are received) the solution is workable.
Using sequence numbers and date can mitigate issues as much as possible
(without solving some weird cases but reducing them as much as possible).
Issue: Should we prompt users to accept changes coming through email?
Not really discussed.
Issue: Share read only
Email will contain items with UUID. Receiving an email will overwrite
read onlyness. This is a sort of a backdoor to read only (possible exploit).
Issue: Merging happens when sharing with a server, not when getting
changes through emails (for those, we use the sequence/timestamp to
overwrite if necessary).
Issue: Chandler should ignore updates sent to itself. Idea of having a
unique identifier per Chandler client so to make the conflict resolution
logic better.
Actions: Mail to the list with more details
----------------------------------------------------
- Plan to use EIM for serialization (Brian)
- Idea of sequence numbers (Jeffrey)
- Multiple change scenario (Brian)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
