[replies to several separate emails below]
[snip]
The biggest con for this is that users are very likely to import or share indefinitely recurring events. So I don't think we can avoid indefinite recurrence in 0.6.
Another solution is to allow them in, and to not generate them for new components.
Both 2445 and 2446 allow for clipping them to some number of instances. And -ALL- implementations that store-expanded-only recurrences clip them now anyway, Each at some unspecified count.
I would suggest always generating them as bounded so that you have control of the clipping.
Strawman proposal 2: The same as proposal 1, but allow users to not set an end date. If no end date is supplied, ...
I assume (who ever said that) meant that you still allow for a DTSTART, no DTEND and no DURATION on recurring instances as allowed by 2445. These are events that exist, and consume no time. (birthday).
> Will get faster "for free" as the repository gets faster. The more
Cons: Slow when creating or modifying large numbers of recurrences, but this
> important "con" is that a user might set up five years of daily exercise
> and then be puzzled five years later when the occurrences stop appearing.
> While it'd be trivial to click on the last occurrence and change the end
> date, it's possible you might not think of doing it. And for more
> infrequent things like birthdays and the like, the lack of repetition
> past a certain point might be non-obvious and therefore more problematic.
Or store some local-only property/parameter that tells the Organizer's CUA to generate and/or send out more when the bounded end is reached.
Or to notify the Organizer via a pop-up (or what ever) so they can elect to extend the object.
--
Doug Royer | http://INET-Consulting.com -------------------------------|-----------------------------
We Do Standards - You Need Standards
begin:vcard fn:Doug Royer n:Royer;Doug org:INET-Consuiting.com adr:;;1795 W. Broadway St #266;Idaho Falls;ID;83402;U.S.A email;internet:[EMAIL PROTECTED] title:CEO tel;work:208-881-0380 tel;fax:866-494-8574 note;quoted-printable:AOL: SupportUnix=0D=0A= MSN: [EMAIL PROTECTED] Yahoo: Help4Unix x-mozilla-html:TRUE url:http://Royer.com version:2.1 end:vcard
smime.p7s
Description: S/MIME Cryptographic Signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
