[horde] Activesync not working

[Michael J Rubinsky]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>>
>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>>>>>
>>>>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>>>>> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>>>>>>> >
>>>>>>> >> Hello,
>>>>>>> >>
>>>>>>> >>  My Activesync is still not working.  Actually its getting  
>>>>>>> worst. Just
>>>>>>> >> upgraded to the latest horde framework with
>>>>>>> >>
>>>>>>> >>  "pear upgrade -a -B- c horde" and NO errors whatsoever. 
>>>> ....
>>>>>
>>>>> --
>>>>> Horde mailing list
>>>>> Frequently Asked Questions: http://horde.org/faq/
>>>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>> Bad news... I created a dummy calendar while keeping my normal (buggy?)
>>> calendar in Kronolith and selected only the dummy calendar for sync with
>>> mobile devices.  Then I added the account on my iphone and sync'ed the
>>> calendar.  All went fine at first.  All events that were in the dummy
>>> calendar were sync'ed on the iphone and vice-versa.  Then over the last
>>> few days I played around by creating & modifying events on the iphone and
>>> all have sync'ed to horde until the last two event which got sync'ed to
>>> horde properly (good dates and times) except it was not created in the
>>> dummy calendar but the real one...
>>>
>>> Sound like AS is confused which calendar to use....
>>
>> Yeah, that makes sense. I think we need to tweak the logic that  
>> determines which calendar to send new events to. The AS protocol  
>> technically only supports a single calendar. So, what we do is  
>> combine all the calendars into a single stream and send them to the  
>> device. This allows all the calendars the user owns to be visible  
>> and *editable* on the device, but *new* events will *always* go to  
>> the user's default calendar.
>>
>> We probably need to either enforce that the default calendar is  
>> always sync'd or if it's not being sync'd, create new events in the  
>> first calendar listed in the sync pref. I would lean towards the  
>> first option.
>
> I think the latter is more intuitive, though it might seem random to  
> the user where the new events go to. If we opt for the first option,  
> we need to exclude the default calendar from the sync calender pref,  
> and explicitly mention that it's always synched, in the prefs  
> screen. I wonder if SyncML does the same, I guess so.


This is now implemented (the former choice).

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org