Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 25819 invoked from network); 21 May 2010 07:27:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 May 2010 07:27:45 -0000 Received: (qmail 86063 invoked by uid 500); 21 May 2010 07:27:45 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 85872 invoked by uid 500); 21 May 2010 07:27:45 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 85859 invoked by uid 99); 21 May 2010 07:27:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 May 2010 07:27:44 +0000 X-ASF-Spam-Status: No, hits=-1431.6 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 21 May 2010 07:27:43 +0000 Received: (qmail 25733 invoked from network); 21 May 2010 07:27:23 -0000 Received: from unknown (HELO ?IPv6:::1?) (127.0.0.1) by 127.0.0.1 with SMTP; 21 May 2010 07:27:23 -0000 Message-ID: <4BF635DA.4030208@apache.org> Date: Fri, 21 May 2010 09:27:22 +0200 From: Stefan Seelmann User-Agent: Thunderbird 2.0.0.24 (X11/20100411) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: LDAP diagnostic tool - GSoC 2010 References: In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Keheliya Gallaba schrieb: > 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 When I look to this picture it reminds of the Wireshark tool. I looks like the "LDAP Proxy Core" only listens to the communication stream. But my understanding, and please correct me if I'm wrong, is that the proxy really intercepts the communication. Another though regarding JNDI and the new client API: I'm not sure if you can work with such high-level API at all. You have to deal with low-level LDAP messages, maybe you have to learn ASN.1. An example: one use case of the tool is to just log the LDAP messages but leave them unmodified. In that case JNDI can't be used because you can't control the message it creates. However you should take a look into the LDAP API code and how it uses the underlying network layer (Apache Mina) to send LDAP requests. Kind Regards, Stefan