Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 52157 invoked from network); 30 Mar 2009 19:30:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Mar 2009 19:30:22 -0000 Received: (qmail 90710 invoked by uid 500); 30 Mar 2009 19:30:22 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 90638 invoked by uid 500); 30 Mar 2009 19:30:22 -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 90630 invoked by uid 99); 30 Mar 2009 19:30:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2009 19:30:22 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [81.169.146.161] (HELO mo-p00-ob.rzone.de) (81.169.146.161) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2009 19:30:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1238441392; l=775; s=domk; d=labeo.de; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: Subject:To:MIME-Version:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=C3FrGwZzEwZXTGXW2+xxvnXaQPriKnofoXeXG7nzzwA=; b=EBX1rxbS3ZgboqGUgs6APhB7SJr6oK8fCjwbWGam4FZSiz2mfYeBDovtVwNFQDm17K1 WN+vjSlN2pnbnAhiyKSwneyuyvLSUokwPTCS8YHbv/2gQV5z2T36DC/EPw1w2fkcTsgcy cVuar8JYZvzWj71vLws9IhMvlPLpZt/UtEM= X-RZG-AUTH: :P3gBc0GmW/MphhhpU4BSj2bmx/Zwgz97J2mNwJqPPUnmUEgIhVdW+Y2Zx4U= X-RZG-CLASS-ID: mo00 Received: from [127.0.0.1] ([88.128.85.154]) by post.strato.de (klopstock mo57) (RZmta 18.28) with ESMTP id w0602bl2UItnmF for ; Mon, 30 Mar 2009 21:29:49 +0200 (MEST) Message-ID: <49D11DAE.1000109@labeo.de> Date: Mon, 30 Mar 2009 21:29:50 +0200 From: Stefan Zoerner User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [Client API] Bind Operation References: <49CF4FE0.9040502@nextury.com> <49CF7567.5040807@gmail.com> <49CFAC1F.9000308@nextury.com> In-Reply-To: <49CFAC1F.9000308@nextury.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Emmanuel Lecharny wrote: > 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. Looks good to me. What about the return value (is it void in all four cases?) and the case that authentication fails. Throws it an exception, and if so, is it derived from RuntimeException (I hope so)? Greetings from Ingolstadt, Stefan