On Tue, 2004-08-03 at 14:44 +0200, Stefan Guggisberg wrote: > 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... > acl ? > > 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. > > 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]
