Ticket #157 (new Defect)
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: | ||
| Port: |
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
Note: See
TracTickets for help on using
tickets.
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.