[Calendar and Contacts Server] #466: Reliable ETag for GET on rolled-up calendar data
#466: Reliable ETag for GET on rolled-up calendar data -----------------------------+---------------------------------------------- Reporter: apm@… | Owner: wsanchez@… Type: Feature | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: -----------------------------+---------------------------------------------- Doing a GET on a calendar collection to get rolled-up iCalendar data as an ".ics" file can be slow on large calendars. Therefore caching it and using HTTP conditional GET by ETags significantly improves performance if the calendar has not been changed. I see that CalendarServer 3.0 is no longer returning an ETag for the calendar collection resource on GET as described in: http://marc.info/?l=calendarserver-dev&m=126270712631748&w=2 So given the discussion in thread above and in Ticket #405, I'm hereby filing a request for a reliable ETag on calendar collections. -- Ticket URL: <http://trac.calendarserver.org/ticket/466> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
#466: Reliable ETag for GET on rolled-up calendar data -----------------------------+---------------------------------------------- Reporter: apm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 3: Important | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: -----------------------------+---------------------------------------------- Changes (by wsanchez@…): * owner: wsanchez@… => cdaboo@… * priority: 5: Not set => 3: Important * type: Feature => Defect Comment: Fair enough -- Ticket URL: <http://trac.calendarserver.org/ticket/466#comment:1> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
#466: Reliable ETag for GET on rolled-up calendar data -----------------------------+---------------------------------------------- Reporter: apm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 3: Important | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: -----------------------------+---------------------------------------------- Comment(by apm@…): Oh ... and one note: The 2.4 implementation of the ETag doesn't really save you any time, since it goes through the entire rolling up of events and only considers the ETag afterwards. It seems to rely on a Twisted asumption that GET and HEAD are always so fast, that it doesn't matter. However, generating rolled up calendar data is not that fast. -- Ticket URL: <http://trac.calendarserver.org/ticket/466#comment:2> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
participants (1)
-
Calendar and Contacts Server