Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 16895 invoked from network); 26 Mar 2009 01:26:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Mar 2009 01:26:15 -0000 Received: (qmail 98481 invoked by uid 500); 25 Mar 2009 23:26:42 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 98451 invoked by uid 500); 25 Mar 2009 23:26:42 -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 98443 invoked by uid 99); 25 Mar 2009 23:26:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2009 23:26:42 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rahul.soa@googlemail.com designates 209.85.218.160 as permitted sender) Received: from [209.85.218.160] (HELO mail-bw0-f160.google.com) (209.85.218.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2009 23:26:32 +0000 Received: by bwz4 with SMTP id 4so289957bwz.25 for ; Wed, 25 Mar 2009 16:26:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=mn2+9KziJRoiQULXLDFaTWtzXJ1gFJFvZRNjMtIG3C8=; b=hHKSFfwZoUyAvGOd65sZys3HXYomzmL7ipRHA0b3UFeOdeXZDnWgPt8WZJDlXVFLEy pVqqQ1Z89dZ2iAtbFPzcgWcXez0HjnxBufI2v1jGTzS/ncM08d4fjq9pGS4JY/LjZRf0 WrnBRSTg/eGI0DbpL0xf9xgPVEJ6NdpBZvZx8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=RMV7s/WSR9OgFWAYhanSgjVsgBQx+cRNVDZ/x/n38a2IB9wyBhH+swYmwT6Gp+5xKI Z31+1chuIeQUzsoeFZaqTsWixG2iyQUC4kBpA4njclwE3dCRXpr26tHM3Rx/Let5XWYJ um8RjY8KYM5mdOYMBlGIMPRXVniK+x3DfK8EE= MIME-Version: 1.0 Received: by 10.204.101.71 with SMTP id b7mr48191bko.107.1238023571828; Wed, 25 Mar 2009 16:26:11 -0700 (PDT) Date: Thu, 26 Mar 2009 00:26:11 +0100 Message-ID: Subject: Initial Draft for gsoc proxy plugin project From: "rahul.soa" To: Apache Directory Developers List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello Devs, I have written an initial draft for gsoc "LDAP proxy plugin" project. Can you please suggest about the modifications (what should be added or should be removed from it)? // quote Title/Summary: LDAP Proxy Plug-in -------------- Abstract: --------- To develop an eclipse plug-in for exposing and storing the exchanged messages between the LDAP server and client for debugging/diagnosing purpose. This plug-in will be encapsulated in Apache Studio. Detailed Description: --------------------- In order to expose message exchange (request/response - such as bind, search, add entry, delete entry, modify entry etc.) between the Directory Server (LDAP Server) and client (Apache Studio), there is a need of proxy tool (initially a debugger tool) which will allow us to analyze the exchanged decoded messages. Furthermore, this proxy should allow us to store the messages in xml format to generate tests based on those recorded requests/responses messages. This proxy will be integrated in the Apache Studio as an eclipse plug-in and will provide the debugging facility "on demand". This proxy plug-in will be able to work with any kind of LDAP server. The basic idea is to extract the exchanged PDU (Protocol Data Unit) and to present them with their decoded values. This will enable us to explore the system to understand how it works by tracing down the request and response and to see what messages we send to and receive from the LDAP server. The future work could be to extend this debugging/diagnostic tool to a real proxy by implementing some additional new features like integrating a LDAP smart load balancer or switch (smartly distribute the connection and search requests based on the namingContext across replica and by taking advantage of already populated cache respectively), failover mechanism (to improve the availability) and security features (filtering mechanism and logging utilities etc). Deliverables: 1. To develop proxy plug-in for Apache Directory Studio with the following features: -> To expose the decoded exchanged messages in UI -> To store the messages in the xml file -> To generate the tests based on the stored messages 2. Testing with LDAP Server and Apache Studio 3. Documentation 4. Future work indication //Unquote Any suggestion will be appreciable. Many Thanks. Best Regards, Rahul