Andreas Hartmann wrote: > We need a centralized, remotely accessible content repository. > I'm not sure if JCR is able to do that, if not we can maybe add > a remote access layer above it.
+1 AFAIK there have been some attempts in the Jackrabbit community to provide remote access. But I think we should do some proper research and come up with a good reasoning what to layer on top of what. In my understanding, JCR is an API in the first place, not a network protocol. In fact I kept asking myself what the differences between a remote filesystem (mounted via SMB or NFS), a WebDAV repository or a SVN repository might me. I keep asking myself wether or not it would make sense to create a SVN-backend for Lenya. Why re-invent the wheel? Regards, Torsten > Michael Wechner wrote: >> Gregor J. Rothfuss wrote: >> >>> Michael Wechner wrote: >>> >>>> There are various things which currently prevent that Lenya can be >>>> clustered. >>> >>> >>> >>> such as? >> >> - Flow, because it's not serializable > > That's a hard one. > >> - Sitetree of default publication, because it cannot be shared within >> the cluster resp. locked >> - "Content Repository" re writing > > That can be generalized to all files Lenya writes to (content, > user base, policies, search index at the moment). > > We need a centralized, remotely accessible content repository. > I'm not sure if JCR is able to do that, if not we can maybe add > a remote access layer above it. > > -- Andreas > > > --------------------------------------------------------------------- > 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]
