Hi, J. Wolfgang Kaltz wrote: > IIUC moving to a "JCR-only" approach means that only content backends > which implement JCR (so right now only Jackrabbit) may be used for > storing content which is handled by Lenya ?
> Other repositories: what about svn ? Wouldn't moving to JCR-only mean we > can no longer support svn as a backend, and thus use Lenya for Apache > sites ? IMO that would be a real shame - please enlighten me if I got > something mixed up :) Aren't we start to mix up things here? To me, the internal storage of content pieces in Lenya at authoring time on one hand and a static export of a site or pieces of a site are two quite different issues. Compare the structure (especially directory layout and filenames) in the file based repository of Lenya today with the URL structure of the live and authoring section of a Lenya website. www.mysite.com/producs/overview.html will *not* be a file named overview in a folder called products today. And a relative link to images/pro01small.jpg in the above mentioned page would resolve to a location in the filesystem of the Lenya instance which is *not* relative to to the page, but in a different root. See what I mean? And by the way do we support direct editing in SVN today? Where a checkin of a document becomes a SVN checkin? Did I miss that? What I am concerned with for quite some time is our URI mangling magic stuff. IMO he have way too much semantics and implicit contracts in our URIs, especially when it comes to embedding (a page and pictures on the page) or linking pieces (internal and external links) together. I was hoping that JCR as a well thought through, standardized and in the near future well known standard API will provide a chance to clean this up and improve. For example, by linking not to a pathname but to a UUID. This would take lots of ambiguity out. Regards, Torsten > Andreas Hartmann schrieb: >> Felix Röthenbacher wrote: >> >> [...] >> >>> Please let me know what you think about the draft moving >>> Lenya away from the filesystem-centric approach to a more >>> powerful usage of the possibilities JSR-170 offers. >> >> >> In theory, it would of course be great to leverage the full >> power of JCR. >> >> Some open questions: >> >> Do we still want to support other repository implementations, >> especially the current source-based approach? >> > > IIUC moving to a "JCR-only" approach means that only content backends > which implement JCR (so right now only Jackrabbit) may be used for > storing content which is handled by Lenya ? > > Other repositories: what about svn ? Wouldn't moving to JCR-only mean we > can no longer support svn as a backend, and thus use Lenya for Apache > sites ? IMO that would be a real shame - please enlighten me if I got > something mixed up :) > > -- > Wolfgang > > --------------------------------------------------------------------- > 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]
