[Tickets #12912] Re: Event handling through ActiveSync

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12912
------------------------------------------------------------------------------
  Ticket             | 12912
  Updated By         | simon at simonandkate.net
  Summary            | Event handling through ActiveSync
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_5_1
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


simon at simonandkate.net (2014-01-16 11:06) wrote:

>> There seems to be very little relationship between the action that
>> was taken and what gets communicated through Horde.
>
> This is not true. Horde is doing *exactly* what the iOS client is  
> asking. The only thing I would agree with here is that when an  
> exception is deleted, it might be confusing to receive the two iTIps  
> - one for the exception being deleted and one for the original event  
> being modified (because the previous exceptions are no longer valid,  
> and the original event series is now active).

OK, it appears to send an invitation as opposed to a cancellation when  
events AFTER the original one is opened, as Apple prompts to "Delete  
this event" or "delete all future events".

So it leaves events prior to the one opened as the delete 'master'.

I'm going to have a play with sequences and events over the next week  
or so, will post back with results.