right, so this means not keeping ACL data on the node itself, as Sriram suggests?
I guess you need seperate nodes to store the ACL data (stored against the UUIDs of the nodes you are protecting) and on startup, load that up into a dirty big in memory map, which the ACL uses. When you add/modify a node, you need to update the ACL data nodes, and flush its cache (or something like that). Does that sound reasonable? On 10/9/06, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
On 9 Oct 2006, at 10:52, Sriram Narayanan wrote: > Are there any other recommendations on writing AccessManagers ? The recommended strategy is to cache the ACL info on startup, and have a listener that updates the cached data on node updated/deletes. This listener would be set up using a session that has full access to the repository. There hasn't been posted any example code to the list yet though. -- Torgeir Veimo [EMAIL PROTECTED]
