Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 64467 invoked from network); 2 Aug 2005 23:02:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Aug 2005 23:02:41 -0000 Received: (qmail 81515 invoked by uid 500); 2 Aug 2005 23:02:40 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 81475 invoked by uid 500); 2 Aug 2005 23:02:40 -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 81462 invoked by uid 99); 2 Aug 2005 23:02:39 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2005 16:02:39 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [193.252.22.20] (HELO smtp12.wanadoo.fr) (193.252.22.20) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2005 16:02:30 -0700 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1208.wanadoo.fr (SMTP Server) with ESMTP id F1FF51C00091 for ; Wed, 3 Aug 2005 01:02:36 +0200 (CEST) Received: from [192.168.0.20] (APh-Aug-102-2-1-32.w193-252.abo.wanadoo.fr [193.252.40.32]) by mwinf1208.wanadoo.fr (SMTP Server) with ESMTP id BBCD61C00085 for ; Wed, 3 Aug 2005 01:02:36 +0200 (CEST) X-ME-UUID: 20050802230236769.BBCD61C00085@mwinf1208.wanadoo.fr Subject: Re: Client library From: Emmanuel Lecharny To: Apache Directory Developers List In-Reply-To: <800df63905080215541a52faf8@mail.gmail.com> References: <175413f5f273d5b3b7beb1727fdf62e8@apache.org> <800df63905080210121b72e2e4@mail.gmail.com> <42EFAE2C.8020400@bozemanpass.com> <800df639050802105872f0c727@mail.gmail.com> <42EFB554.5060605@bozemanpass.com> <800df63905080211134c524287@mail.gmail.com> <42EFF00E.5030203@bozemanpass.com> <800df6390508021536111edad6@mail.gmail.com> <1123022766.11037.11.camel@wkslx01.iktek.com> <800df63905080215541a52faf8@mail.gmail.com> Content-Type: text/plain Organization: iktek Date: Wed, 03 Aug 2005 01:02:36 +0200 Message-Id: <1123023756.11037.23.camel@wkslx01.iktek.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) 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 On Tue, 2005-08-02 at 18:54 -0400, Marc Boorshtein wrote: > Did I miss something? I thought JNDI was the "apacheds" client API? > Or was the original question about accessing apacheds directly inside > of an app (as opposed through the LDAP protocol). > > Marc JNDI is perfect 99% of the time. But we may have a more specific API, (like JLDAP) that does the same work. I don't see any way to access apacheds without using the LDAP protocol, actually. But we perfectly could build an API that access apacheds through LDAP protocol, without using JNDI. So if there is a need to do so, it's possible.