[Freeassociation-devel] default INTERVAL parameter

[dothebart]

having run the test-suite this is what I found:  

########## Test recur parser                       
(8) ##########
not ok 209 -
FREQ=YEARLY;UNTIL=20000131T090000Z;INTERVAL=1;BYDAY=-1TU,3WE,-4FR,SA,SU;BYYEAR
DAY=34,65,76,78;BYMONTH=1,2,3,4,8
# test failed: ""
#          at: regression.c:2291
#      got:
FREQ=YEARLY;UNTIL=20000131T090000Z;BYDAY=-1TU,3WE,-4FR,SA,SU;BYYEARDAY=34,65,7
6,78;BYMONTH=1,2,3,4,8
# expected:
FREQ=YEARLY;UNTIL=20000131T090000Z;INTERVAL=1;BYDAY=-1TU,3WE,-4FR,SA,SU;BYYEAR
DAY=34,65,76,78;BYMONTH=1,2,3,4,8
not ok 210 -
FREQ=DAILY;COUNT=3;INTERVAL=1;BYDAY=-1TU,3WE,-4FR,SA,SU;BYYEARDAY=34,65,76,78;
BYMONTH=1,2,3,4,8
# test failed: ""
#          at: regression.c:2296
#      got:
FREQ=DAILY;COUNT=3;BYDAY=-1TU,3WE,-4FR,SA,SU;BYYEARDAY=34,65,76,78;BYMONTH=1,2
,3,4,8
# expected:
FREQ=DAILY;COUNT=3;INTERVAL=1;BYDAY=-1TU,3WE,-4FR,SA,SU;BYYEARDAY=34,65,76,78;
BYMONTH=1,2,3,4,8  

thats the Interval missing we're talking about, right?  

So it seems as if our own test-suite says Benoit might be right?
  
>  Fr Aug 07 2009 04:16:42 EDT von  "Patrick Ohly" <patrick.ohly at gmx.de> 
>Betreff: Re: [Freeassociation-devel] default INTERVAL parameter
>
>  On Tue, 2009-08-04 at 08:34 +0200, Benoit Schmid wrote:
>  
>>The ical rfc states that the default value for INTERVAL parameter
>> is one.
>> 
>> Therefore in you code you have implemented:
>> if(recur->interval != 1){ ...
>>
>>http://mxr.mozilla.org/comm-central/source/calendar/libical/src/libical/icalre
>>cur.c#570
>> 
>> Unfortunately this causes problems for programs that does not
>> implement the default value.
>> 
>> We use Lightning client with a Synchronica SyncML gateway.
>> Because of this interval not provided anymore, our smart phones
>> do not synchronize the recurrent anymore.
>> 
>> Lightning developers told me that it could be only
>> changed in libical.
>> 
>>

>  As a developer of a SyncML client (and soon server), I tend to disagree
> with this.
> 
> If I understand it correctly, the Lightning client sends valid iCalendar
> 2.0 which is either not parsed correctly by the Synchronica server or
> passed through by it in a way which then confuses the smart phones. In
> both cases the correct solution is to improve the server.
> 
> The second best solution is to tweak the outgoing format of the SyncML
> client. libical is not designed for this. What if one recipient wants
> INTERVAL=1 and another chokes on it (unlikely, but who knows...)?
> INTERVAL is perhaps a bad example, there might be better ones.
> 
> If a SyncML client wants flexible iCalendar 2.0 *and* vCalendar 1.0
> support, then I recommend the Synthesis SyncML engine [1]. That's what
> SyncEvolution uses now.
> 
> [1] http://lwn.net/Articles/333441/
> 
> -- 
> Bye, Patrick Ohly
> -- 
> Patrick.Ohly at gmx.de
> http://www.estamos.de/
> 
> 
> 
>
>------------------------------------------------------------------------------
>
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>
> trial. Simplify your report design, integration and deployment - and focus
>on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Freeassociation-devel mailing list
> Freeassociation-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freeassociation-devel
> 
>
>
>  

  

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/libical-devel/attachments/20090807/746979e0/attachment.html>