Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: local policy)
From: "David Moss" <david.moss@infoflow.co.uk>
To: <users@jackrabbit.apache.org>
Subject: Advantages of building tree structure
Date: Fri, 17 Nov 2006 11:12:59 -0000
Organization: Infoflow
Message-ID: <000001c70a39$56f4dcd0$1801a8c0@intelligentsia.local>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C70A39.56F726C0"
Thread-Index: AccKOVbMQuzNvpYRRWS5a8I1wjF6Nw==

------=_NextPart_000_0001_01C70A39.56F726C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 
This might sound like a simple question, but what advantage is there in
building a tree structure to store my data?
 
If I'm storing a single type of data 'documents' that is distributed to
'recipients' (be it groups or users).  What advantage is there in building a
user / group / role hierarchy and retrieing documents through that as
opposed to simply storing documents with an attribute indicating the
recipient?
 
I realise this would result in a flatter tree structure, which I've read
elsewhere is not handled so well by jackrabbit.  What's the reason for this?
Are attribute values indexed at all?
 
Many thanks,
 
David.


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
------=_NextPart_000_0001_01C70A39.56F726C0--