[Cosmo] Re: indexing all components in a calendar resource?
lisa at osafoundation.org
Tue Feb 14 12:47:44 PST 2006
You know, I can't believe I blocked that out. Should have just
glanced at an example in the spec before spouting off. I remember
initially wanting the object stored to be just a VEVENT (nothing
outside) but that would have been an iCalendar violation. I'm now
tempted to suggest that CalDAV should make storing that extraneous
stuff optional, but I do think that would get us into even more
trouble. Ugh, ick.
In cosmo, can we store that stuff -- and return it in requests --
without indexing it? Can we mark certain things as being "not
indexed" and thus if a client queries on them we have to dig through
the actual data? This might be a reasonable future optimization, only.
On Feb 14, 2006, at 10:03 AM, Cyrus Daboo wrote:
> Hi Lisa,
> --On February 14, 2006 9:26:32 AM -0800 Lisa Dusseault
> <lisa at osafoundation.org> wrote:
>> Cyrus, I still don't understand how VERSION would even get
>> uploaded to a
>> VCALENDAR component in a CalDAV server. Are you saying that a
>> would PUT a VCALENDAR component resource to be a child of a calendar
> The calendar object resources stored in a calendar collection are
> ENTIRE iCal objects - i.e. they contain the VCALENDAR wrapper
> around the actual event/to-do components. If that were not the case
> they would not be valid iCalendar data in and of themselves.
> Cyrus Daboo
More information about the Cosmo