[CalendarServer-dev] [CalendarServer] #319: A solution is needed when max_allowed_instances is exceeded.

[CalendarServer]

#319: A solution is needed when max_allowed_instances is exceeded.
-----------------------------+----------------------------------------------
 Reporter:  apm@…            |       Owner:  wsanchez@…        
     Type:  Defect           |      Status:  new               
 Priority:  5: Not set       |   Milestone:                    
Component:  Calendar Server  |    Severity:  Serious           
 Keywords:                   |  
-----------------------------+----------------------------------------------
 With the ability to create events longer into the future the possibility
 that a user will create an event with more than "max_allowed_instances"
 (currently 1000) increases.

 From instance.py:

 # The maximum number of instances we will ezpand out to.
 # Raise a TooManyInstancesError exception if we exceed this.
 max_allowed_instances = 1000

 ... which will make events disappear from instance 1000 or not get created
 at all if you place the mother event sufficiently far back in the past.
 If - say - your default_future_expansion_duration is 2 years, you
 currently cannot create a daily recurring event with a motherevent before
 ~ april 2008.
 Or if you create a daily recurring event today, it will no longer work
 after 1000 days.

 I see no good solution to this without some mechanism for the user to
 clean up old calendars, so the don't unnecessarily contain - say - 5 year
 old daily events.

-- 
Ticket URL: <http://trac.calendarserver.org/ticket/319>
CalendarServer </>
HTTP/WebDAV/CalDAV Server