Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 77841 invoked from network); 21 May 2010 05:27:56 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 May 2010 05:27:56 -0000 Received: (qmail 75771 invoked by uid 500); 21 May 2010 05:27:56 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 75572 invoked by uid 500); 21 May 2010 05:27:56 -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 75563 invoked by uid 99); 21 May 2010 05:27:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 May 2010 05:27:56 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of akarasulu@gmail.com designates 209.85.161.66 as permitted sender) Received: from [209.85.161.66] (HELO mail-fx0-f66.google.com) (209.85.161.66) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 May 2010 05:27:50 +0000 Received: by fxm7 with SMTP id 7so189902fxm.1 for ; Thu, 20 May 2010 22:27:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=YqsI/PO/LOReKgpNDBXZuqBwfbG3T9kkEx9J0lvPgVI=; b=ibECrZcK5/STQzdQ0CkWEd6F56v1pmPvzWKgt/3B6ZRrKOHAGSVc5UNZneN71SOGUA qVlt21VbZTVK3vUZWg8GhyCI+xXSX4h+2FZ4tRKRxYcruH/IYsH9y14YZlqp21oEh239 KRQ/Miq9yKPLdqeVLT3mAKExocuD1Sh3lWqL8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=FUtoSluBhxbMEMNtO8+05pkcpBcVyt8NEjQzIgry3s6mFO+nO9xAIuoMtwQDdqkp8S ck45QUWPfN+rpCxaDShyObFUOLuL073g9w9eKfE+7EIv7k3EP74lNaDyi3whpiQi6Czq 1UUtXkNWY767t74vIi0YidgDtarkkBZz20l2A= MIME-Version: 1.0 Received: by 10.239.160.197 with SMTP id e5mr84202hbd.201.1274419649675; Thu, 20 May 2010 22:27:29 -0700 (PDT) Sender: akarasulu@gmail.com Received: by 10.239.160.66 with HTTP; Thu, 20 May 2010 22:27:29 -0700 (PDT) In-Reply-To: References: Date: Fri, 21 May 2010 08:27:29 +0300 X-Google-Sender-Auth: 2wxzxo45__vc4Rw04DfOdLCtyyI Message-ID: Subject: Re: LDAP diagnostic tool - GSoC 2010 From: Alex Karasulu To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=001485f27c2c838056048713f2c7 X-Virus-Checked: Checked by ClamAV on apache.org --001485f27c2c838056048713f2c7 Content-Type: text/plain; charset=ISO-8859-1 Can you show something with data flow steps in this diagram so it's easier to understand it? On Fri, May 21, 2010 at 7:45 AM, Keheliya Gallaba < keheliya.gallaba@gmail.com> 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, > > -- > Keheliya Gallaba > http://galpotha.wordpress.com > http://twitter.com/keheliya > -- Alex Karasulu My Blog :: http://www.jroller.com/akarasulu/ Apache Directory Server :: http://directory.apache.org Apache MINA :: http://mina.apache.org To set up a meeting with me: http://tungle.me/AlexKarasulu --001485f27c2c838056048713f2c7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can you show something with data flow steps in this diagram so it's eas= ier to understand it?

On Fri, May 21, 201= 0 at 7:45 AM, Keheliya Gallaba <keheliya.gallaba@gmail.com> 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 t= hought of implementing the initial phase with JNDI and moving to the new cl= ient API later. Please send your suggestions for this approach, and about t= he existing code components I can reuse, from Directory Studio.

[1] http://code.google.com/p/dirstudio-ldap-p= roxy/wiki/ArchitectureDiagram

Thanks,

--
Keheliya Gallaba
http://galpotha= .wordpress.com
http://twitter.com/keheliya



--
Alex KarasuluMy Blog :: http://www.jrolle= r.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu
--001485f27c2c838056048713f2c7--