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 piccinatto@ibest.com.br
 designates 200.181.68.97 as permitted sender)
Content-Disposition: inline
Content-Transfer-Encoding: binary
Content-Type: text/plain
MIME-Version: 1.0
From: "hsp" <piccinatto@ibest.com.br>
To: dev@jackrabbit.apache.org
Cc: Torgeir Veimo <torgeir@pobox.com>
Subject: Re: Mixin values.
Date: Tue, 04 Apr 2006 10:47:25 -0300
Message-Id: <20060404134725.9F39427C61@angmar.ibest.com.br>

Sorry if my question is so obvious, is a shame that it is not for me.
The acl you said is like 'access control list' ? How could I implement it? Is there a ready support in jackrabbit for this? How many information must have in this key.
I would mind this better, please help me about it. I'm a begginer.
Thanks
Helio 


>On Tue, 2006-04-04 at 10:07 -0300, hsp wrote:
>
>> Anyway, following your example, when I want to give access to a node
>> with id=XXX to an user USER, I must create a new propertie, called XXX
>> into the node the USER belongs to, for ex:
>
>> >On Tue, 2006-04-04 at 10:26 +0200, Marcel Reutegger wrote:
>> >> 
>> >> Using the node id as a property name allows you to use the regular
>> >> api 
>> >> to get the access control you are looking for.  
>
>Marcel is talking about storing the acl in a map keyed on the nodeid.
>That map would then be externally to the repository itself and you don't
>have to do any repository query / lookup to retrieve the acl. 
>
>It's still possible to store acl's in the repository and just update an
>external map using a listerener on the repository. This listener would
>then read the data in the way you suggest and update the map.
>
>-- 
>Torgeir Veimo 
>
>