Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of tsirkin@gmail.com designates
 209.85.215.42 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=TsOaCZ04BhZ8Wm8L8EYDF7ur+QAR0XjEffTwArtuE5xK+xsaa7W2pspya9lByXsibc
         HvBBitYX8rFff6kX3yz1IBXUPKxnY1+fYGNISw2lIQ9GOBM4J2lPplOsVUDe5WE2eMrm
         708XG69QfC0ure+FyjJsGCPasRVNtRJtcnvNY=
MIME-Version: 1.0
Date: Wed, 20 Oct 2010 15:54:29 +0200
Message-ID: <AANLkTimutM0Tz7HqbXjmX70n8fFuwWNC467MaK91mF-K@mail.gmail.com>
Subject: Is Jackrabbit right for me
From: Tsirkin Evgeny <tsirkin@gmail.com>
To: users@jackrabbit.apache.org
Content-Type: multipart/alternative; boundary=0015174c34ac92ccb304930cbf2b

--0015174c34ac92ccb304930cbf2b
Content-Type: text/plain; charset=UTF-8

I have the following task for which i am researching JCR/Jackrabbit .
This would be an internally used system.
Mostly this is a document management system tied to the organization's
 structure.
Organization -> department -> sub department etc.
Since this is a university we are talking about, at each level we have
staff, at different levels/roles,
and students .
The staff is responsible for maintaining it's (sub) department document's
and it's (sub)department student's documents.
That basically means that each department will have a lot of "student" nodes
and a lot of documents stored for
the department itself.
Different roles can have read or writes privileges.
Now ,unlike a content management system, here I  have heavy write/update
load with
concurrent reads and writes.
What I am mostly worried about is a concurrency problems I have read about
 .
What I understand is that Jackrabbit does not support :

[1] Concurrent request while a session have write rights will block and
evaluated in single thread.
That means that several users logged in as write enabled (and those would be
the most of my users)
will have their requests executed in a single threaded mode.

[2] Concurrent writes are not allowed to the same node's children even if
this is a child addition.
If all this is right ,it is a real show stopper.

I gathered all this from reading this thread:
http://www.mail-archive.com/users@jackrabbit.apache.org/msg16089.html
and this blog:
http://blog.tfd.co.uk/2010/10/15/jackrabbit-performance/
plus some other resources but those are the main one.

Although JCR and Jackrabbit seems to be a real fit for my hierarchy based
task it,because of JCR's
hierarchy nature, it may well be that it is not that good fit because other
problems and I better look for other
JCR or not JCR based solutions.

Thanks
Evgeny

--0015174c34ac92ccb304930cbf2b--