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)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=jDe7E/mzuRY3G3zXkhiuJcA3E0kbrJ5TTZ96rlEvWkJWZm/L7c//cB2BSLtBuRAAI+
         lJcA4JVONQKzZ9RKm7j4BSGfj8h+qR7nRE4mWfxB3wWfbXP++OGOcvOEIClhUuSywR22
         iaRDlKohRY9JENqyyu3AeG1mIbMcJ5mwBqPe4=
Message-ID: <4BF633B9.3060002@gmail.com>
Date: Fri, 21 May 2010 09:18:17 +0200
From: Emmanuel Lecharny <elecharny@gmail.com>
Reply-To: elecharny@apache.org
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: LDAP diagnostic tool - GSoC 2010
References: <AANLkTimJORVszSRnhmmFfiytujzuCH7doHvYsA7Ws_h-@mail.gmail.com>
In-Reply-To: <AANLkTimJORVszSRnhmmFfiytujzuCH7doHvYsA7Ws_h-@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 5/21/10 6:45 AM, Keheliya Gallaba wrote:
> Hello everyone,
>
> I have come up with an architecture diagram [1], with the help of Seelmann,
> for the LDAP diagnostic tool explaining the functionality of the core. I
> thought of implementing the initial phase with JNDI and moving to the new
> client API later. Please send your suggestions for this approach, and about
> the existing code components I can reuse, from Directory Studio.
>
> [1] http://code.google.com/p/dirstudio-ldap-proxy/wiki/ArchitectureDiagram
>
> Thanks,
>
>    
Looks good. Some hints :
- The Ldap message Extractor should be completed with a session manager 
layer, if you want to be able to track one user specifically.
- This proxy should work for any LDAP server not only for ADS

Otherwise, I would rather use the new API instead of JNDI : it will be 
easy, and more accurate. If it leads to some modifications on the API, 
that would also benefit this part of the server. "Eat your own food"

-- 
Regards,
Cordialement,
Emmanuel L�charny
www.nextury.com