Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of michael.neale@gmail.com
 designates 66.249.82.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=enLcLF0eDjgCdvdLBcNNdXcA8oYtJPAu6G7oNWMexIzRaACFJ1cu0ST6wpYSbxt5LMsXOYb0SJZUezp6zJLfCl35MOyxw7o7ESXmKwRIv4A5CHmQf5kSFQhx7pHTAWKcbvBwhHEpmz8J54ndL27sB0v8KXsxjqYnoCPr8oNyDrQ=
Message-ID: <96ab3ced0609040136q235ac34w5680130e603ed4f8@mail.gmail.com>
Date: Mon, 4 Sep 2006 09:36:27 +0100
From: "Michael Neale" <michael.neale@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Newbie seeking a leg up
In-Reply-To: <63c452f80609031708u2bb38820m834ae72314f1c829@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_114576_23411697.1157358987696"
References: <63c452f80609031708u2bb38820m834ae72314f1c829@mail.gmail.com>

------=_Part_114576_23411697.1157358987696
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Sean.

I was also looking in to how Jackrabbit behaved for my needs (I had some
specific numbers I was looking for) - the best thing I found was to just
build up some basic test code to load up enough nodes to verify it would do
roughly what I needed (which was a bit more effort then I thought, but I got
there in the end).

The moral of the tale: try it ! hack away and see how it behaves. For a
large flat structure like you are suggesting, it seems that save operations
can be a little slow (but slow is relative, in terms of user experience its
still fast) for large numbers of nodes under the same parent, but otherwise
seemed fine (I was also concerned with versioning a lot, which I am not sure
concerns you).

On 9/4/06, Sean Dynan <seandynan@bigfoot.com> wrote:
>
> Hi all
>
> I am just starting to investigate Jackrabbit as the content repository
> for an application and some advice from the experts would seriously
> speed up my evaluation.
>
> The problem domain in question is somewhat similar to a corporate mail
> server:
> - Large user base
> - Frequent user reads and writes, mostly of text and
>    images. By 'frequent' I mean usage on a par with an
>    email client
>
> Where it differs from the mail server comparison:
> - Users can query the repository by keyword and expect
>    rapid results (think Google)
> - Users can query each other's information stores
> - No upper bound to the physical size of the repository
>
> Right now, I don't envisage a deep-noded store. Think of many Items,
> each containing content and a little bunch of metadata (e.g. datetime,
> list of keywords, etc.). The email analogy would be many email
> messages, each with a body and a header.
>
> I am also thinking of implementing each user's content store as a
> Workspace. Each workspace would have two top-level nodes hanging from
> its root: Private and Public. Then each of those two nodes would
> contain many, many content Items.
>
> Is there anything so far that wouldn't be well served by building on
> top of Jackrabbit?
>
> Am I right in assuming (given my ideas above) that cross-workspace
> queries are perfectly possible, and that all that is required is a
> separate, logged-in Session to each one?
>
> Can you envisage any issues (performance or otherwise) with my
> pitifully meagre outline? Any sage words of advice on how to best
> start architecting my repository?
>
>
> Many thanks!
> --
> Sean Dynan
>

------=_Part_114576_23411697.1157358987696--