The point about using an industry standard is that everyone can pick
their own favourite implementation on the standard.
In other words, you can use Jackrabbit instead of Priha. Otherwise,
it would make no sense to use JSR-170, now would it?
(Priha makes for a good default implementation simply because it's
lightweight, has NO mandatory dependencies and is much better aligned
with our current repo format than Jackrabbit. It's much like the
same situation as with, say HSQLDB vs MySQL. Both have their own
uses. Have you noticed that we ship with HSQLDB right now instead of
MySQL? Funny, that ;-) )
/Janne
On 3 Nov 2008, at 01:26, Murray Altheim wrote:
Janne,
I remember part of the conversation regarding your choice in
developing
Priha versus a more direct incorporation of Apache JackRabbit, but I
wonder if I could have you elaborate a bit on that, and if that
earlier
decision still holds. The reason I ask is that we are moving towards a
requirement that our backend storage be something more compatible with
some of our other existing services, and I've been looking at using
JackRabbit across several services. If JSPWiki 3.0 was to use
JackRabbit
rather than Priha I'd have a much easier time selling the idea.
I know that JackRabbit is much "heavier" than might be necessary, but
what do you see is the principal reason not to use it rather than a
custom solution such as Priha?
Thanks very much,
Murray
......................................................................
.....
Murray Altheim <murray07 at altheim.com>
=== = =
http://www.altheim.com/murray/
= = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk
= = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
