418345 - Decide how to handle Generation property properly - CalIInvitation and Layered Event models

Status: RESOLVED FIXED

(Calendar :: Internal Components, defect)

Description

[cmtalbert]

The Generation propery gives us visibility into when an event has changed.  Sometimes, we have to fake that the event has not changed in order to clone it properly in order to work with it.  We do this currently for iTIP processing. The proper way to handle this might be with the notion of layers in the UI and with a storage cache of event invitations across all calendars - something like a calIInvitationManager which we can always use to get the latest version of the invitation without user modifications (so that we can send it back to the organizer for example).

This is a "design" bug.  It was generated because of this comment by Daniel in bug 379198: 
calIItemBase::generation is the internal version of the item much like the
SEQUENCE number. We could avoid generation checks by tweaking it like you did
above, but this will discard any changes that may have occured in the meanwhile
(e.g. user added some notes to an invitation). We need to clarify this,
possibly UI needed.

Comment 1

[Daniel Boelzle [:dbo]]

I've decoupled SEQUENCE from generation, and SEQUENCE is only bumped on *major* changes by the organizer. Thus I think this bug is fixed with changes on bug 457203.