Stefan Guggisberg schrieb:
To find out if it is possible to build the complete webdav layer on top of jsr-170 is to give it a try. I don't know much about jsr-170, but I didn't find the following webdav-features in jsr-170:Daniel Florey wrote:
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.
it's certainly not trivial but i don't see why it shouldn't be possible. all required building blocks are there in JSR 170: versioning (closely sync'ed with JSR 147), observation, JTA support, observation, search...
Locking:
- timeout of locks
Acl:
- handling of principals
- aggregation of actions (permissions in jsr terms)
deltaV:
- Baselines, Activities...
I think this is a fundamental different approach.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.
my idea would be to expose the JCR api on the server and on the client.
i've implemented a transparent RMI layer for the JCR api for a previous
version of the ri. the client side JCR implementation could of course use
any transport protocol, that's up to the implementation.
Currently the Slide project is WebDAV-centric. There is a mature testsuite that runs with different webdav-servers, a webdav commandline client etc.
The goal is to have a first class WebDAV-server that supports as many aspects of the WebDAV protocol as possible. If we can achieve a broader WebDAV-support, we can use the growing number of nice WebDAV-clients around. If subversion is getting more WebDAV-compliant and we are implementing more of the deltaV features, we can even use the fine subversion clients.
A lot of people are using Slide to make their content repository WebDAV-enabled. So the bridge from Slide to legacy repositories should be simplified.
IMO jsr-170 should become the default repository/store if it supports all the WebDAV features.
So, to find out how to proceed, we need an expert who knows all about WebDAV *and* the jsr-170 spec...
Cheers, Daniel
WebDAV could IMO be used as an alternative for accessing the resource-centric content in the repository.
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]
