I thought of another problem with Forwarding events as messages
with .ics files attached.
Recipients of this Forward in Chandler will render the Forward item
as an event invitation.
In the off-change that the Forward-Event is added to a Calendar that
the Chandler recipient shares with the Chandler sender, how will we
reconcile the incongruity in Stamps?
The Chandler sender will regard the Forward as a pure message item.
The Chandler recipient regards the Forward as an event, the Chandler
sender regards the Forward as a message.
It looks like without more sophisticated support for Clusters and/or
per-sharee stamps, Forwards are doomed to live in ignominy where they
could potentially screw up the sender's calendar with multiple events
that represent the same event, but aren't actually connected to each
other via UUID or cluster-relationships etc.
However, this is most definitely an edge-case and I'm personally okay
with noting it as a known issue and moving on to bigger problems.
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design