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
 74.125.82.50 as permitted sender)
Message-ID: <512BF2E6.2080606@gmail.com>
Date: Tue, 26 Feb 2013 00:25:26 +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: Release soon...
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi guys,

I will probably try to cut a release tomorrow, as may bugs have been
fixed lately. It will still be a milestone, as I still want to do some
big modification in both the backend data structure and in the API :
getting rid of the StringValue/BinaryValue classes.

I do think that we shuld only manipulate byte[] in the server. All in
all, String are just UTF-8 encoded byte[], so there is no reason to
manipulate Strings. It will solve many issue, like the one we have with
binay AttributeType which has a SUBSTR matchingRule (currently, we can't
filter any entry based on such matching rule), and it will also run
faster : we won't have to do a byte[] -> String conversion when we
receive a request and convert it back to a byte[] when storing it in the
backend, and the exact opposite double conversion for any Attribute's
value we pull from the backend to return it to the client.

It will take quite a while to fix that, as it's used everywhere, so I'd
liek first to have a release done.

Thoughts ?

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