[Cosmo] Exception When PUTting Event, Slowness when PUTing recurring event

[Cyrus Daboo]

Hi Brian,

--On December 22, 2005 9:45:52 AM -0500 Brian Moseley 
<bcm at osafoundation.org> wrote:

>> Doing something like that will require changes to ical4j to allow
>> expansion to be limited to a maximum count, a change in the indexer to
>> include in the time-range field an indicator that the limit was or was
>> not reached, and a change to the time-range term comparator to catch the
>> limit being exceeded.
>
> in addition to the above recommendation, you earlier said there was one
> other thing that needed to be done to finish cosmo's reports support (i
> believe it was something about generating a report for all resources
> within a collection; i'd have to dredge up the email to be sure).

I will provide a detailed list of things still to do with reports. The 
major items are:

1) Support for Depth in reports. Currently the reports are hard-coded to 
Depth: 1. i.e. they assume you are running them on a calendar collection.

2) Support for the new timezone behaviour defined in draft -09. This 
requires either parsing the new timezone element in the report request, or 
using the timezone defined in the new property on calendar collections. One 
complication with this is that reports have to generate separate queries 
for each calendar collection, as the timezone has to be used to generate 
floating time ranges that are encoded into the xpath query. Since timezones 
may be different in each calendar collection, separate queries are required 
for each, with a merge of all results for the actual response.

3) Indexing of components other than VEVENTs. At the very least VTIMEZONE 
needs to be included. Since you do not support VTODO/VJOURNAL etc right now 
those could be left out.

> is that truly the sum of work that gives us full reports support through
> the upcoming draft, or are there any other concerns?

Pretty much so. I will do one more pass over the draft and compare with 
what's been done in Cosmo.

> do you have enough time left on your contract to do these things, or will
> i be adding them to my own schedule? :)

I'm afraid I am pretty much out of time, just the scripts left to do.

> when can i look forward to seeing those test scripts and so forth?

I am finishing that off right now. Should commit something later today. It 
may be worth contributing these to Calconnect ioptest group as I'm sure 
other folks could make good use of the tests too.

> thanks for all your help, by the way. all the jackrabbit custom querying
> stuff, and the recurrence expansion stuff especially, would have been a
> nightmare for me to figure out on my own. ;) now that you've got a solid
> base, i think i can maintain it.

It certainly helped having done all that stuff once before. Knowing the 
pitfalls and how to work around them sped things up a lot. I certainly hope 
you find it easy to maintain.

Note that I start new employment on 2nd January. Whilst I am unlikely to be 
able to help out in coding, I will certainly be available for questions 
regarding the work I have done, and will be participating as usual in ical 
mailing lists to help with any general issues etc

-- 
Cyrus Daboo