Stefan Guggisberg schrieb:
Daniel Florey wrote:
This would be great if jcrri would provide all requirements to build a
WebDAV layer on top of it (including all the current drafts). As see
slide as a bunch of java software related to WebDAV. If we could achieve
this using jcrri I'd vote for it. Stefan (currently working on the
jcrri) stated in his mails that there might be some problems regarding
the content model.
sorry daniel, you got me wrong. i was saying that building the WebDAV layer
on top of the JCR api is relatively straight forward. in fact, we already
did a quick&dirty implementation that is running on top of the jcrri.
connect your WebDAV client to http://jsr170tools.day.com/crx/repository
and give it a try.
Yes, I've seen this and it looks very promising. But as far as I can
tell, it will be much more complicated to build the deltaV, acl,
transaction, notification and dasl specs on top of jsr-170.
implementing the JCR api on top of the WebDAV client lib or the Slide api
on the other hand would be quite difficult because of the different content
models of JSR 170 and Slide/WebDAV; WebDAV/Slide's model is resource centric
whereas JSR 170's model is fine granular, i.e. it supports unstructured,
semi-structured and well-structured content.
you can model WebDAV content very easily in JSR 170 but you can't model
all different kinds of JSR 170 content in WebDAV.
I see. But IMO it is a key feature of the 3.0 release to have a single
API that can be used on client and server side (see 3.0 design approach
in the wiki). So how can we achieve this when using JSR 170? Just curious.
Daniel
regards
stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
