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 (herse.apache.org: domain of ole.ersoy@gmail.com designates
 66.249.82.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=E4JgL38ygfvcoLwJ6CKzQYzNpN+W7DteMeyO9fa83xihkCsSyVUkwdO//GbTZG8OBHb3+6Li2bB2KQtwVFCIzpb3jVTqpk1M5utGq3UWmCyUIN505aPZxBnwHMNIXEIyYdwM4N/vsiDNF3U3bKE9nCu9ybgC3w4cdUxPbv5zZ+4=
Message-ID: <4648B3C7.2010601@gmail.com>
Date: Mon, 14 May 2007 14:08:55 -0500
From: Ole Ersoy <ole.ersoy@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070302)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Spring LDAP 1.2 RC1
References: <a1b4a6610705140657k516969b5m3b85721ba8525bf4@mail.gmail.com>
 <d45b08f00705141118j62e6a72ci85150831db932e6b@mail.gmail.com>
In-Reply-To: <d45b08f00705141118j62e6a72ci85150831db932e6b@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

That would really rock if they agree.

We talked about cleaning up
shared-ldap a while back.

I think if we find a common approach
that all developers could agree on,
then shared-ldap could become a great utility
for all of us.

My suggestion was basically take everything
out of the closet and put everything back nice
and neat according to predefined standards (Testing,
naming conventions, etc.)

I suggested using a new closet to house cleaned
code so that we know what's been cleaned up, although
it's still the same closet (Just a digital replication of it :-) )

This enables developers to proceed at their leisure,
both in refactoring the existing server code
to use the "Cleaned" utilities and adding more utilities.

Anyways I think if we get all our ideas down,
create a checklist out of those, and
create the "Ideal" concept for shared utilities
it will be easy for other developers to come on board.

Maybe we should invite them to that type of discussion?

 From our previous discussion it sounded like
people would rather recreate the wheel than
poke through shared-ldap so visibility and simplicity
of searching the code should be a major priority,
making use the library as attractive as possible.

Jakarta Commons has a pretty good model for that I think.
Maybe we should identify the gap with shared-ldap and
make that an initial target, and then encourage other
developers to improve that target?  For instance with
spring the ldap stuff is front and center.  We should probably
have something similar...so mina, ads, shared-ldap, etc...

If we think it's a good idea, I'd be glad to nudge them,
although they may feel even more encouraged if it comes from
someone with more ADS history (Emmanuel - Alex hint hint :-) ).

Cheers,
- Ole


Emmanuel Lecharny wrote:
> Those guys have written a complete Ldap wrapper, including their own DN 
> parser.
> 
> They should use shared-ldap. We should tell them to use it. We should do 
> some effort to share this piece of code :)
> 
> Emmanuel
> 
> On 5/14/07, *Ersin Er* <ersin.er@gmail.com <mailto:ersin.er@gmail.com>> 
> wrote:
> 
>     http://www.springframework.org/node/459
> 
>     --
>     Ersin
> 
> 
> 
> 
> -- 
> Regards,
> Cordialement,
> Emmanuel L�charny
> www.iktek.com <http://www.iktek.com>