[Cosmo-dev] candidate protocol/interop bugs for 0.8

[Mikeal Rogers]

The other CalDAV server implementations seemed to have started  
thinking it's a good idea to simply store iCalendar components you  
don't recognize rather than rejecting them outright, while still  
failing on unrecognized attributes of recognized components. This is  
due to the rate at which components are being added, most of them  
being used in the wild before even a draft specification has been  
released to the public.

I heard that part of the benefit to moving to the newest iCal4j was  
that we could not use "strict" mode and we might be to able to do  
this. I know we have a bunch of bugs for this but are we planning to  
go down this road in 0.8?

-Mikeal

On Jul 18, 2007, at 12:19 PM, Brian Moseley wrote:

> i've created a list of protocol- and interop-focused enhancements and
> bugs to consider for 0.8 at
> <http://chandlerproject.org/Journal/BrianMoseleyNotes>.
>
> anyone interested in these topics, please review this list and let me
> know if you think i've forgotten anything. feel free to file new bugs
> to cover concerns that are not already tracked in bugzilla.
>
> thanks!
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev