[Tickets #12592] Re: Allow shared calendars to be the default calendar

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12592
------------------------------------------------------------------------------
  Ticket             | 12592
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Allow shared calendars to be the default calendar
  Queue              | Kronolith
  Version            | Git master
  Type               | Enhancement
-State              | New
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-08-20 21:47) wrote:

This was restricted on purpose. There are a number of issues:

1) No way to mark an event as read only. Obviously can be worked  
around by limiting only to calendars that the user has PERMS_EDIT to,  
but what happens when a shared calendar's permissions are changed so  
that the user no longer has access to edit events, but can still read  
them? There is no way to indicate this to the client. The only  
solution would be to verify permissions on each synchronized calendar  
on every sync request.

2) The same event can be represented in multiple calendars. I.e., two  
calendars can have an entry that represent the same UID. This happens,  
e.g., when a meeting request sent from one user is added to another  
calendar. If the event organizer has access to both calendars, and an  
event is edited on his/her client - which copy of the event is  
modified on the server? What about if the non-organizer edits the  
event on their calendar? That change would be picked up by ActiveSync  
since you are synching the calendar, so essentially, a non-organizer  
would have the ability to change the organizer's copy of the event.

What happens if an external meeting request is accepted on two  
calendars the user can sync? They are two separate copies of the same  
event. The result of editing the copy on the client would be  
undefined. Not to mention that the organizer field in current code is  
bound to horde usernames, so from the POV of the ActiveSync client the  
current user would be seen as the organizer, and thus editing the  
event and sending out itips would be allowed.