[...]
>>But that should be possible using a generic JCR browser
>>or editing tool. IMO this argument is not sufficient for
>>providing a filesystem-based implementation (which requires
>>maintenance).
>>
>>
>
> everything needs maintenance ;-) So why did you start a(nother) generic
> API in the first place and not use JCR directly within your suggested
> API ;-)
For the following reasons:
- clarity (model exactly what the repository should be capable of)
- ease of use (reduce flexibility)
- protection (don't allow to tinker with the repository content directly)
>>We once agreed on a JCR-only approach. I don't want to start
>>the discussion again,
>>
>
> I would, because I have realized there are still a lot of
> people wanting to use the FS and I think it makes a lot
> of sense in many cases and that's the situation many people are
> in.
>
> As said before we don't have any clue what problems lie ahead re JCR
> and although I am big fan of JCR and keep pushing it for some years now,
> I still want an alternative and Lenya is able to provide such an alternative
> very easily.
I doubt that we can provide it "very easily", but this depends
on one's point of view what it should be capable of.
>> I just wanted to point out the option
>>of implementing a file-system based repository (I'm sure that
>>would have been the next question). The (in)famous phrase
>>"feel free to implement this" applies,
>>
>
> maybe you don't have to implement this, but please give other people
> the freedom to do so, especially if they are ready to invest
> the time and already invested a lot of time into this project.
Agreed. I just expressed my priorities.
>> but IMO we should focus
>>on the JCR-based implementation to end up with a stable and
>>performant product after a reasonable timespan.
>>
>>
>
> what is a reasonable timespan? Didn't we want to release 1.4 last autumn?
Maybe we should release ASAP and defer the new repo API to 1.6.
> I see the light at the horizon, but not with a fully tested JCR where
> we can tell people with proper honesty, please rely your publications on
> this ...
>
> But I can stand behind it with a FS based system, where we use a
> Source/RepositoryFactory
> and make it very simple to switch to JCR at any time (and other
> repository implementations)
> at any time. This is why I am working hard to get rid of all direct FS
> dependencies which
> will lead to a perfect world as you probably wish.
I have more confidence in JCR than in the current file-system based
repository layer in 1.4-dev. But maybe some automated tests will
increase my confidence.
Thanks for your comments! I have the feeling that there's really
a light at the horizon re. 1.4 :)
-- Andreas
--------------------------------------------------------------
Andreas Hartmann [EMAIL PROTECTED] +41 1 272 9161
Wyona AG, Hardstrasse 219, CH-8005 Zurich
Open Source CMS http://www.wyona.org http://www.wyona.com
--------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
