David Nuescheler wrote:
well, actually i would not store the iCalendar body as a data property,
but "simulate" an iCalendar file serialization in the webdav layer.
once somebody PUTs any iCalendar file i would automatically deserialize it into the iCalendar properties.
does that make sense?
yep, it does. that strategy will support CalDAV iff the properties can reliably be reconstituted into the exact same iCalendar body every time it is requested.
cool, do you have already have an idea about the structure of the iCalendar nodetype(s)?
not yet - i'm still working on integrating Jackrabbit and jcr-server with a security framework (Acegi Security) and establishing a web ui for managing users and access control. when that's working, i'll be ready to start looking at what needs to be done for CalDAV support.
