[kronolith] Updating My Calendar.

[Jan Schneider]

Zitat von Andrew Morgan <morgan at orst.edu>:

> On Fri, 9 Oct 2009, Wayne Catterton wrote:
>
>> Hi,
>>
>> That bug link you sent is all just a blur, I mean from reading that, I
>> still have no idea of how this thing works.  It's not rocket science,
>> can't someone write up any documentation that is clear and concise?  or at
>> least write the program in a way that people can understand?
>
> <snip>
>
>>> The behavior is as expected, though maybe not as desired. See also
>>> http://bugs.horde.org/ticket/8288
>
> Reading through that bug report (and I think your issue), I'm a bit  
> confused as well.  I think maybe I don't understand the calendar  
> model Kronolith is using.
>
> Most of my calendar interactions are with a MS Exchange system that  
> the rest of campus uses.  When I receive a meeting invitation from  
> them, I choose "Accept and add to my calendar".  This adds the event  
> to my calendar and (I think) emails an iCal response back to the  
> originator. This sounds very similar to the Horde situation when I  
> do not have access to the originator's calendar.
>
> When I have access to the originator's Horde calendar (as described  
> in the bug), what is the reason that Horde only tries to update the  
> originator's calendar entry?  Isn't the correct behavior to:
>
> 1. Update the originator's event with my attendee status (possibly  
> by iCal email response if I do not have Edit access)

*Only* by iCalendar response, because there is no guarantee that both  
users are on the same Horde server, or on Horde at all.

> 2. Add the event to my own calendar for notification/tracking purposes

It's not that easy, because iCalendar events handled by iTip and also  
events internally used by Kronolith are identified by a GUID. If we  
just store the event in the user's calendar, it's either not a GUID  
anymore, or we need to generate a new GUID which disconnects those two  
events.

Of course there are possible solutions, which is what this ticket is  
about. It may not be rocket science, but it's sufficiently complex to  
not be done with a single line of code. And it's not top priority of  
any of the Horde developers at the moment. Well possible that it might  
be top priority for some users, but we only have 24-hour-days like  
anyone else, and we're just a small number.

I know that you know that, Andrew, but the tone of your message was  
more  objective and motivating to reply to than the other. :)

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/