Projects
Wiki     Timeline     Roadmap     Browse Source     View Tickets     New Ticket     Search

Ticket #157 (new Defect)

Opened 3 years ago

Last modified 10 months ago

Clean-up CALDAV:free-busy-set property when there are non-existent calendars

Reported by: wsanchez@… Owned by: cdaboo@…
Priority: 2: Expected Milestone: Later
Component: Calendar Server Severity: Other
Keywords: Cc:

Description

2/12/07 11:33 AM Cyrus Daboo:

Clients may not properly remove calendars from CALDAV:free-busy-set property when a calendar is deleted. The server ought to remove non-existent calendars itself - either automatically when a calendar is deleted, or when that property is accessed for scheduling

Change History

Changed 3 years ago by wsanchez@…

2/12/07 2:20 PM Wilfredo Sanchez: Where a calendar is deleted is probably better, in that someone may create another new calendar with the same name, and the old value probably shouldn't linger. That's an edge case, but it's easily covered. Also, we may want to avoid having to do an extra stat() or other runtime check while looking up the property.

3/28/07 12:04 PM Wilfredo Sanchez: We may also want to verify the list any time it is otherwise edited and clean it up then.

Changed 3 years ago by wsanchez@…

  • milestone changed from 1.0 to 1.1

Changed 3 years ago by wsanchez@…

  • milestone changed from 1.1 to 1.2

Changed 3 years ago by wsanchez@…

  • milestone changed from 1.2 to 1.x

Changed 2 years ago by wsanchez@…

  • milestone changed from 1.x to 2.x

Changed 10 months ago by wsanchez@…

  • milestone changed from CalendarServer-2.x to Later
Note: See TracTickets for help on using tickets.