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 handling ideas
To: Apache Directory Developers List <dev@directory.apache.org>
References: <561C010F.4090401@gmail.com>
 <CABzFU-e77y6SrDDjjZULdZ61m_zBUWZx8hFfnbhm2Rn1cTe0hw@mail.gmail.com>
From: =?UTF-8?Q?Emmanuel_L=c3=a9charny?= <elecharny@gmail.com>
Message-ID: <561CB8D4.9020901@gmail.com>
Date: Tue, 13 Oct 2015 09:55:00 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: 
 <CABzFU-e77y6SrDDjjZULdZ61m_zBUWZx8hFfnbhm2Rn1cTe0hw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Le 13/10/15 07:29, Kiran Ayyagari a écrit :
> On Tue, Oct 13, 2015 at 2:50 AM, Emmanuel Lécharny <elecharny@gmail.com>
> wrote:
>
>> Thoughts about value handling in the API and Server
>> ---------------------------------------------------
>>
>> <snip>
>> Another idea would be to simply hide the byte[] unless we need to
>> convert them to a String, which can be done when needed. We need to
>> convert the values when we do a normalize (this happens when we want to
>> compare the value to another one), or a compare. We also need to run
>> every value through the PrepareString methods (and PrepSASL for the
>> userPassword) before saving them to the disk.
>>
>> but AFAIU this conversion happens multiple times if not stored, so I still
> prefer converting once and use the stored value later onwards

Actually, once converted, we should keep a copy of the converted value,
to avoid any further conversion.