jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <field...@gbiv.com>
Subject Re: considering use of jackrabbit
Date Tue, 12 Jul 2005 15:28:41 GMT
On Jul 12, 2005, at 7:36 AM, Franco Krattiger wrote:

> we're considering using Jackrabbit for a medium scale web-application
> that we are currently in the planning stage for.

That's nice.

> having perused the open issues on Jira i'm somewhat unsure whether
> it's a wise decision to make use of the product prior to the first
> official release.

I think you should try using it.  If you find problems, report them,
preferably with the fix.  That's what we do at Apache.  Eventually,
the problems (if any) will be very hard to find, but we can only
get there one volunteer at a time.

> the majority of the severe issues seem to pertain to the versioning
> code.  as versioning support is not a requirement for our application,
> i could live with that limitation.

That's good -- we wouldn't want you to keel over and die on us.

> JCR-160 (query index not in sync with workspace) worries me, however.
> searching is, not surprisingly, a key requirement for our app... if
> the indexes run awry that's a bad thing :(

Yep, we think so too.

> so basically, i have the following questions:
> - generally speaking, can Jackrabbit in its current state be considered
>   for production use?

We have not released it yet.  We won't release it until we think it
is ready to be released.

>   considering the open issues, this obviously would require workarounds
>   or an outright avoidance of certain functionality.  i guess i'd like
>   to know if you guys are reasonably confident that the codebase 
> doesn't
>   harbor any more severe bugs beyond those already known and reported.

That's a silly question.  Do you require that of your own source code?

> - for those familiar with JCR-160: just how quickly do the indexes 
> drift
>   out of synch?  in my app, jackrabbit will probably see less than 100
>   mutations/day... if the indexing creeps up rather slowly, it might be
>   feasible to work around it by reindexing on a nightly basis until a
>   fix comes along...

I highly recommend testing it in practice, before deployment, with
your own set of use-cases.  Please report any findings back to the
project and, eventually, we will all collaborate on making it better.

However, if what you want is business assurances or OEM-style
products, then you should seek out a business that will give
you such assurances (my employer is one, but this is not intended
as an advert in any way).  Open source projects are about collaboration,
not about giving vendors free support.


View raw message