> >> How about defining a formal remote protocol for JCR instead? A JCR > >> explorer is of course a useful tool, but having a defined, formal > >> protocol to interact with a JCR repository would be ideal. I'm > >> thinking something similar to webdav but more appropriate for JCR > >> repositories. > > > > I am not sure, whether I understand you correctly. Currently the > > Jackrabbit protocol has an RMI library, which allows plain-JCR > > remoting > > over RMI. In addition there is a simple WebDAV servlet, which allows > > filesystem-like access over WebDAV to the repository and there is a > > JCR > > WebDAV servlet, which in fact remotes the JCR API over WebDAV using > > defined WebDAV functionality such as DASL etc. > > > > The webdav protocol doesn't map fully to the JCR data model. And RMI > is not really that useful when the client is not a Java client. > > But I guess it opens up a lot of questions, I guess. How do you send > JCR data over the wire? XML or JSON? afaik there are already some drafts of implementing the JCR SPI using rjax. but this would rather be a jackrabbit GSoC topic, right?
regards, toby -- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
