[Chandler-dev] Recurrence in sharing

[Jeffrey Harris]

Hi Folks,

Normally I'd have a Skype conversation with Morgen about stuff like
this, but in an attempt to be more list-oriented, I'll put it in an
email. ;)

I've been thinking about recurrence and sharing.  I was looking at
rewriting some of the import code to do a better job of preserving
existing items that don't need to be changed.  This got me thinking
about our approach to recurrence in sharing.

I think, to preserve data integrity, we need to have a different
approach to recurrence sharing than other areas.  Ideally, we'd first
create a journal of server changes to a recurring event (if any exist),
then we'd compare them to a journal of changes since the last sync.

This process is fairly complex, and most of the details are quite
specific to recurrence.

I'd like to move much of recurrence conflict handling out of the
ICalendarFormat import and export layer and deal with it at a higher
level in the sharing process.  Morgen has been understandably reluctant
to add this complexity to sharing, but I think we're going to be running
into more confusing and difficult recurrence related merging bugs if we
don't work with recurrence more directly.

Sincerely,
Jeffrey