A branch has been created :
https://svn.apache.org/repos/asf/directory/apacheds/branches/trunk-with-dependencies-AP
On 12/13/10 6:00 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 12:41 PM, Emmanuel Lecharnywrote:
Hi guys,
I'm resuming the APs implementation. I have had a new idea this mor
On 12/13/10 6:00 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 12:41 PM, Emmanuel Lecharnywrote:
Hi guys,
I'm resuming the APs implementation. I have had a new idea this morning
about the best way to handle them.
Currently, we had devised about too possible options
1) Processing the entri
On 12/13/10 6:00 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 12:41 PM, Emmanuel Lecharnywrote:
Hi guys,
I'm resuming the APs implementation. I have had a new idea this morning
about the best way to handle them.
Currently, we had devised about too possible options
1) Processing the entri
On Mon, Dec 13, 2010 at 7:00 PM, Alex Karasulu wrote:
> To think this through let me just for the record go through the way search
> interacts with the administrative model subsystem. I won't consider
> base/object scoped searches.
>
>(1) On the way into the server a search may have some eval
On Mon, Dec 13, 2010 at 12:41 PM, Emmanuel Lecharny wrote:
> Hi guys,
>
> I'm resuming the APs implementation. I have had a new idea this morning
> about the best way to handle them.
>
> Currently, we had devised about too possible options
>
> 1) Processing the entries while adding a new AP
> The
On 12/13/10 1:28 PM, Stefan Seelmann wrote:
Hi Emmanuel,
the lazy evaluation sounds interesting, great idea.
Just to clarify:
You are talking only about the process to determine which AP and ACIs
are applied to an entry (which is done by evaluating all AP subtree
specifications), right?
Right
Hi Emmanuel,
the lazy evaluation sounds interesting, great idea.
Just to clarify:
You are talking only about the process to determine which AP and ACIs
are applied to an entry (which is done by evaluating all AP subtree
specifications), right?
The concrete evaluation of the ACI must always be don
Hi Emmanuel,
Interesting idea!
A great combination of both original solutions into a single one...
I like the idea of lazy evaluation and the fact that the administrator can, if
he wants it, go back to solution #1 by simply searching (objectClass=*) under
the newly created/updated AP after it
Hi guys,
I'm resuming the APs implementation. I have had a new idea this morning
about the best way to handle them.
Currently, we had devised about too possible options
1) Processing the entries while adding a new AP
The idea is that when we add a new AP (or delete an existing one, or
modify
