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 (athena.apache.org: domain of elecharny@gmail.com
 designates 72.14.220.154 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding;
        b=EOExsoxFGz7f44EiYIfxBiYnJ/ZYIpxeVljNCLYMXbrrOOpgrOAF27iKNxclbktss5x8rEsFHnyTIUjsp7l7bCWZSd2KA8FALBdUILbGQG7yEcVV9uYiT7SqQ4eAzr8co3W36ghJo45rXQcPW5Y3hVC7hmz/jUpVBBisF/sqZ/Y=
Message-ID: <47B5BD75.2030808@gmail.com>
Date: Fri, 15 Feb 2008 17:27:33 +0100
From: Emmanuel Lecharny <elecharny@gmail.com>
User-Agent: Thunderbird 1.5.0.14pre (X11/20071023)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: [ServerEntry] Report
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi guys,

we are almost done with Phase II : usiage of ServerEntry all over the 
server.

I just migrated the JNDI SearchResult to use our own ServerSearchResult, 
so now, the core is not using anymore JNDI structure internally, except 
on the top and bottom layer (protocol and backend).

There are a few things to do yet :
- Strip the core from any JNDI layer and create a new sub-project 
(server-jndi) which will be the JNDI layer. Doint that will help a lot 
because we will have a pure server accepting requests directly from the 
LdapProtocol layer, without having to deal with JNDI stuff. No more 
DirContext...

Of course, from the user perspective, as the JNDI layer won't change, 
the server will still be usable as it was previously.

- Decouple the backend from the core, and use ServerEntry internally.

That means we will serialize ServerEntries instead of Attributes, 
leading to a major modification of the database content. We will provide 
some tools to migrate the database, of course.

We also have to decouple the backend totally, so that it will be much 
easier to write partitions using any kind of storage (currently, this is 
possible, but it is quite complex).

Another big advantage is that we will be able to add a intermediate 
cache system, more efficient than the one we have.

Alex is working on this part, and is progressing fast.

Once all this will be done, we will switch to phase III, where new 
features will be implemented.

It took a bit longer than expected, but this is the price to pay to keep 
the server stable between each commit (our politic is to ensure that if 
someone want to grab the code, he will be able to run it).

Thanks for your attention !

-- 
--
cordialement, regards,
Emmanuel L�charny
www.iktek.com
directory.apache.org