[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    [Kde-pim] KArm and KOrg using same file
From:       Mark Bucciarelli <mark () easymailings ! com>
Date:       2003-09-02 14:02:35
[Download RAW message or body]

If KArm can use an iCalendar file, it's a safe bet that (some) users will want 
to point KOrganizer and KArm to the same file.  This is how I would expect it 
to work.  (There is one KArm bug report requesting this feature.)

Libkcal reads/writes the entire ics file.  So, the following sequence causes 
data loss:

1. open ics in korg
2. open ics in karm
3. make change in korg
4. make change in karm
5. save karm
6. save korg

So, how to avoid data loss?

1. Have Korg and KArm lock the ics file when they open it.

2. Implement rudimentary conflict resolution in korg and karm.  (For example, 
last write wins, non-conflicting deletes and adds are preserved.)

3. Leave as is and document it.

4. Add a new iCal storage implementation that only changes the iCalendar 
objects it modifies.

5. Other ideas?

Regards,

Mark
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]