Daniel Gomez Brito wrote:
I believe that's the right response but I have some doubts because CalDAV RFC 
states that if the time interval overlaps the original start and end times of 
an overridden instance, that instance should be returned in the response.
Here's the paragraph (http://tools.ietf.org/html/rfc4791#section-7.6):
{{{
   A CalDAV client that is only interested in the recurrence instances
   that overlap a specified time range can request to receive only the
   "master component", along with the "overridden components" that
   impact the specified time range, and thus, limit the data returned by
   the server (see CALDAV:limit-recurrence-set in Section 9.6.6).  An
   overridden component impacts a time range if its current start and
   end times overlap the time range, or if the original start and end
   times -- the ones that would have been used if the instance were not
   overridden -- overlap the time range, or if it affects other
   instances that overlap the time range.
}}}

What's the rationale behind this?

This might be a good question to ask on the caldav list, but I can give my thoughts. The purpose of the limit-recurrence-set element in the query (i don't know of any clients that use this), is to limit the number of overridden instances to return. I guess the idea is that if a recurring event has 100 overridden instances over a 2-year period, but the time-range you are interested in is only a week, it wouldn't make sense for some clients to receive all 100 overridden instances. Instead, they should only receive the master, plus any overridden instance that impact the time range. "Impact" means it either overlaps the time range, or the original time overlaps, in which case the client needs to know this.

So in this case, the time-range you are using doesn't overlap any instances so nothing should be returned. Even if you used limit-recurrence-set with the same time-range, the response should still be empty for this example.

-Randy


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to