Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: Value processing on the server (was Re: Directory Studio:
 Backslash in DN breaks studio)
To: dev@directory.apache.org
References: <295E4926-9E28-4BD6-BB29-0580EE7ABB96@unboundid.com>
 <56E072AF.4000408@gmail.com> <56E1EE0F.4000802@stefan-seelmann.de>
 <56E20EBF.8010309@gmail.com> <56E34CB7.5020308@gmail.com>
From: Stefan Seelmann <mail@stefan-seelmann.de>
Message-ID: <56E3DE84.1060509@stefan-seelmann.de>
Date: Sat, 12 Mar 2016 10:16:52 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56E34CB7.5020308@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 03/11/2016 11:54 PM, Emmanuel Lécharny wrote:
> We could question the rational behind the normalization being done
> preemptively when we receive the data. All in all, we will return
> entries as they were injected, without normalization, and most of the
> Entry's values will never need to be compared, thus won't need
> normalization.
> 
> As I said, normalization is mainly needed for comparisons. So why do we
> normalize *all* the values ?
> 
> This is a choice made early in the Server's design. For the values that
> are going to be compared, we whave three options :
> -1- normalize when we initially receive the data
> -2- normalize the value only when we need to compare it
> -3- normalize the value when we first need it, and keep the normalized
> value in memory, to avoid following normalizations.
> 
> All in all, this is a balance, and we decided a long time ago that
> having the normalized available at all time was way simpler, and
> potentially more efficient.

I think it is good as it is, I don't see that we need to change it.
Especially let's avoid option 3 which would introduce even more complexity.