Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of marcel.reutegger@gmx.net
 designates 213.165.64.20 as permitted sender)
Message-ID: <44322DCB.1080407@gmx.net>
Date: Tue, 04 Apr 2006 10:26:51 +0200
From: Marcel Reutegger <marcel.reutegger@gmx.net>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: dev@jackrabbit.apache.org
Subject: Re: Mixin values.
References: <20060403151112.4B08C2BC7A@webemail04.ibest.com.br>
In-Reply-To: <20060403151112.4B08C2BC7A@webemail04.ibest.com.br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hsp wrote:
> So, let me see if I got what you said. I have to store in the user
> nodes a propertie per each node the user has rights to access, for
> ex: Node user=getnode(userid); user.setProperty(nodeid,"read/write");
> 
> 
> Would be nearly this way? So the query will test if the usernode has
> the property with the nodeid name and the value with the right
> allowed.

As I wrote in an earlier post, I suggest you should *not* use a query to 
  find access control information. performance will probably suffer if a 
query is called on every item access.

Using the node id as a property name allows you to use the regular api 
to get the access control you are looking for.

regards
  marcel