Roy T. Fielding wrote:
No, just use normal HTTP methods. PUT with a calendar media type creates a collection by that name with a default representation of the calendar, containing links for adding new entries (POST) and identifying existing entries (which can be obtained via GET and changed via PUT and DELETE). There is no need for resource- specific additions like MKCALENDAR and OPTIONS. Everything that needs to be communicated can be described directly within the calendar media type rather than in HTTP protocol changes.
i tend to agree with you, though i'm sure the CalDAV authors have a rebuttal that i haven't considered ;) anyway, this is getting offtopic for jackrabbit; maybe it will continue on ietf-caldav, maybe not. thanks for the input tho. i'm pretty excited to actually check out jackrabbit and give it a whirl.
