[prev in list] [next in list] [prev in thread] [next in thread] 

List:       horde-sync
Subject:    Re: [sync] ActiveSync, Tasks and DeadOccur
From:       John Bieling <john.bieling () gmx ! de>
Date:       2018-03-31 21:23:20
Message-ID: 12849d1f-4f96-c77a-6781-85201d39fd4e () gmx ! de
[Download RAW message or body]

Thanks for you feedback, Michael. I will go with the boolean value, but 
it will be trial-and-error I guess :-)

John




On 3/31/2018 9:07 PM, Michael J Rubinsky wrote:
>
> Quoting John Bieling <john.bieling@gmx.de>:
>
>> Hi,
>>
>> has any of the horde EAS developers experience with the DeadOccur tag 
>> of EAS for tasks? The Microsoft documentation is very thin and I have 
>> not yet been able to understand, what this tag is doing and what it 
>> is for.
>
> From what I understand, that tag is used as a flag to indicate that a 
> Task object represents a specific occurrence of a recurring task, as 
> opposed to the object representing/defining the entire series. I 
> remember being somewhat confused as to how the value worked, however, 
> as the documentation from MS is pretty weak. IIRC, I think it was 
> Zpush, simply takes this tag as a boolean value.
>
>> Follow up question: Does horde support this feature? (So I could test 
>> my EAS client against a horde server)
>
> Horde currently ignores this tag, however. Implementing this is on my 
> ever growing list of todos once I find the time...
>
>
>>
>> Thanks for your help
>> John
>> -- 
>> sync mailing list
>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>> To unsubscribe, mail: sync-unsubscribe@lists.horde.org
>
>
>
>

-- 
sync mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: sync-unsubscribe@lists.horde.org
[prev in list] [next in list] [prev in thread] [next in thread]