Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates
 209.85.212.180 as permitted sender)
Message-ID: <51273BC8.20107@gmail.com>
Date: Fri, 22 Feb 2013 10:35:04 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
Reply-To: elecharny@apache.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Substring filter : how to improve their use ?
References: <51266410.9050803@gmail.com>
 <4648C0CE9B4E48679C67F2D07B2BB8B6@gmail.com>
In-Reply-To: <4648C0CE9B4E48679C67F2D07B2BB8B6@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le 2/22/13 8:59 AM, Ludovic Poitou a écrit :
> Hi Emmanuel,
Hi Ludovic
>
> You might want to eval the scope after the filter rather than initially.
> In most real life deployments, applications are searching for a single user, like (uid=elecharny), as a subtree through the whole directory. The scope becomes irrelevant then.
It will be disacarded as we will have only one candidate (or a few) that
match the uid filter, understood.
> So checking the scope first adds processing of no value.
For us, it's just a matter of pulling a number from an index, which is
just a call to a method accessing the Rdn index to fetch the base oject,
but again, it will contain the number of direct children and the number
of descendants, so it's fast (especially if it's in cache).

Now, if a filter like (cn=elecharny returns 0 or 1, we can avoid such a
call, that's for sure. So I will apply the suggestion, and add the scope
*only* if the number is below a certain threshold (5, 10 whatever).

Very good suggestion ! Brillant !


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com