Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 96982 invoked from network); 29 Mar 2009 17:13:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Mar 2009 17:13:33 -0000 Received: (qmail 70657 invoked by uid 500); 29 Mar 2009 17:13:32 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 70584 invoked by uid 500); 29 Mar 2009 17:13:32 -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 70576 invoked by uid 99); 29 Mar 2009 17:13:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Mar 2009 17:13:32 +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 elecharny@gmail.com designates 209.85.220.168 as permitted sender) Received: from [209.85.220.168] (HELO mail-fx0-f168.google.com) (209.85.220.168) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Mar 2009 17:13:23 +0000 Received: by fxm12 with SMTP id 12so1644681fxm.25 for ; Sun, 29 Mar 2009 10:13:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ugc75/uT1ERreZ8LBXYzZwOvPVxah/gQ8tX9LJ9ycck=; b=l+mVmZeKLzD7Q69a+fHjH2SmRgQtfAeMqCMx3GYH1dQril0NpsdUwUv7yKRIc0CHgg mLPK5kv8x+iJQDDmIu2qGd1+156u4whKPzfmcaCpbHcyiUzIhifi53A5umR3RLSjqeL6 s8hTWadGHDgW988Y4WUhDww4IIHPSRn31UZlc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=V2EbocHx9hSIRXGgzCiHJ1T3OT+I2KQG1LseAMM3rKfGd3QzAI9vZePoiuxwpwAUfC wZZTPHiXAgbYnsXT/i6sQlbyxuOTfqTfjXLEk/sRixiL7oyppmgW8BtOFiiLW2lpOKoY qMBXsLrGbtcV7DDt2LvWs+3lM4nFY12qgo700= Received: by 10.223.113.200 with SMTP id b8mr3204819faq.84.1238346782767; Sun, 29 Mar 2009 10:13:02 -0700 (PDT) Received: from ?192.168.0.2? (vol75-3-82-66-216-176.fbx.proxad.net [82.66.216.176]) by mx.google.com with ESMTPS id 21sm1927663fkx.19.2009.03.29.10.13.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 29 Mar 2009 10:13:02 -0700 (PDT) Sender: Emmanuel Lecharny Message-ID: <49CFAC1F.9000308@nextury.com> Date: Sun, 29 Mar 2009 19:13:03 +0200 From: Emmanuel Lecharny User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: Apache Directory Developers List Subject: [Client API] Bind Operation References: <49CF4FE0.9040502@nextury.com> <49CF7567.5040807@gmail.com> In-Reply-To: <49CF7567.5040807@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, some first thought about the bind operation. I propose 4 methods : - bind() for an anonymous bind - bind(String name) for an unauthenticated bind (this is a special case described in RFC 4513, par 5.1.2) - bind(String name, String credentials) - bind(String name, byte[] credentials) Those two methods are standard bind with a credential as a String or byte[] We may define a few others, assuming we may want to use some controls. We also have to deal with SASL bind. -- -- cordialement, regards, Emmanuel L�charny www.iktek.com directory.apache.org