Tobias Strasser wrote:
both. along with the JCRWebdavServer part comes a very simple WebDAV servlet, that exposes the repository in a file-system like way. meaning, nt:file is mapped to a non-collection-resource, everything else mapped to a collection. most of the webdav operations should work. the JCRWebdavServer will also support DeltaV methods for versioning.
sounds cool. all there any WebDAV parts that you are specifically planning to ignore or that you feel will be especially troublesome? if so, why?
i suggest you take a look at the stuff that is already contributed. you are probably the better person to judge what else is needed. further you need probably decide, if the calendar data is stored in a unstructured way, defined by the cal application, or if CalDAV needs a predefined nodetype set for this.
CalDAV will most likely need to define new node types. beyond that, i can't say for sure, as i have to refamiliarize myself with the draft and do some more investigation of JCR.
my biggest area of concern is the CalDAV requirement for WebDAV ACL support, since it doesn't seem to map very well to JCR, which appears to have a more restricted privilege set and no mechanism for extending privileges. any thoughts there?
not yet. please keep in mind, that jackrabbit is a reference implementation. the primary goal is to make it working according to the spec.
of course. i'm not going to need clustering anytime soon (or ever, maybe). i just want to know if anything inherent to jackrabbit's design would prevent that feature from being added down the road. that doesn't seem to be the case, but i'm not intimate with the project yet.
thanks for your comments!
