[kronolith] write organisation calender in user's default calender

[Michael J Rubinsky]

Quoting Ralf Lang <lang at b1-systems.de>:

> Am 19.04.2012 15:18, schrieb Michael J Rubinsky:
>>
>> Quoting Vikas Parashar <vikas.parashar at fosteringlinux.com>:
>>
>>> Hello,
>>>
>>> Can any body let me know how can i write a common calander in
>>> user's default calander.
>>
>> Not 100% sure what you mean here. If you want to know if you can
>> copy an existing, shared, calendar into a user's personal calendar
>> - then the only way to do that via the UI is to export the shared
>> calendar and re-import it into the user's calendar. This might
>> cause issues with having duplicate UIDs if the shared calendar will
>> remain accessible by the user.
>>
>> Perhaps if you let us know what exactly you are trying to
>> accomplish we can help some more.
>>
>>
>
> I don't know if this fits the case but my users have recently raised
> the same question. We manage per-team system shares and syncing
> appointments between horde and their desktop client / pda / phone does
> not work smooth in this setting.
>
> One problem is, for ActiveSync they need to maintain copies of
> appointments in their "personal" default calendar and the device is
> agnostic of where the appointments come from. As a result, users which
> create appointments through their client device need to copy/move them
> to the correct calendar in a separate step. As far as I know, Horde
> cannot do anything about this but it generates a certain level of user
> frustration.

Agreed that this is frustrating, but there is really nothing we can do  
from Horde's side. The main issue here is that the ActiveSync protocol  
only supports a single calendar. We merge all events from all  
user-owened, writable calendars so that all of the events can appear  
on the device. This works so long as the calendars are user-owned and  
writable since there is no notion of a read-only event in ActiveSync.  
Attempting to modify a read only event would cause the client to  
continue to attempt to send the change until it gives up and throttles  
the entire sync session. The problem with opening this up to any  
shared calendars, even if writable, is that there is a chance that  
there are multiple copies of the same event visible (the UID is the  
same). Such a case would happen when the user accepts a meeting  
invitation to a meeting originally in one of the shared calendars.

> I suspect Caldav r/w support would circumvent part of the problem as
> the client device would "know" which calendar an event belongs to.
>
> Any feedback "how to do it right" is welcome.

Unfortunately, there is no way to do it right using the currently  
available sync protocols. If you are feeling adventurous, you could  
hack the code to allow shared calendars to be sync'd, but you would be  
on your own...

> Any clues how to turn
> this into an argument for sponsoring Feature X is welcome too.

You could consider sponsoring the completion of the mobile view of  
Kronolith, which would give you access to all calendars - but would  
obviously not have native device integration for things like alarms.

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6096 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/kronolith/attachments/20120426/75e3e083/attachment.bin>