From dev-return-6849-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Sat Jul 16 13:25:50 2005 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 62156 invoked from network); 16 Jul 2005 13:25:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jul 2005 13:25:49 -0000 Received: (qmail 44265 invoked by uid 500); 16 Jul 2005 13:25:49 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 44195 invoked by uid 500); 16 Jul 2005 13:25:48 -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 44182 invoked by uid 99); 16 Jul 2005 13:25:47 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jul 2005 06:25:47 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of aok123@bellsouth.net designates 205.152.59.71 as permitted sender) Received: from [205.152.59.71] (HELO imf23aec.mail.bellsouth.net) (205.152.59.71) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jul 2005 06:25:43 -0700 Received: from ibm66aec.bellsouth.net ([65.80.200.112]) by imf23aec.mail.bellsouth.net with ESMTP id <20050716132544.EMKD15241.imf23aec.mail.bellsouth.net@ibm66aec.bellsouth.net> for ; Sat, 16 Jul 2005 09:25:44 -0400 Received: from [172.16.1.39] (really [65.80.200.112]) by ibm66aec.bellsouth.net with ESMTP id <20050716132544.LIQO3975.ibm66aec.bellsouth.net@[172.16.1.39]> for ; Sat, 16 Jul 2005 09:25:44 -0400 Message-ID: <42D90AD8.7050502@bellsouth.net> Date: Sat, 16 Jul 2005 09:25:44 -0400 From: Alex Karasulu User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [server] Where is LDAP decoded? References: <800df639050715160457eb116a@mail.gmail.com> In-Reply-To: <800df639050715160457eb116a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Marc Boorshtein wrote: >I'm trying to track down where the ldap messages are decoded from >binary into the objects that are used and passed into the protocol >handlers. Could someone point me in the right direction? > > That would be within the directory/shared/ldap/trunk/apache-provider. We have a provider architecture for decoding LDAP messages. The Snacc4J provider was recently replaced by the apache-provider with minimal changes to the message framework within the ldap-common jar because of this pluggable provider design. HTH, Alex