Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 209.85.219.180 as permitted sender)
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=Qo98myOrbw6gVlbd8DPLegBbaR4FQWemIaX4TQ7G+9QscFbceItsbHMY7R7173J0bC
         mVCHctI9OvKqNth9e2OkLXuMBsrwSX0XLjNXxgoWCnSWVqZV3y8+e68hlhhkHCklI0yd
         XPznLEOuTt/QjzNk9YHq6gl8R8n806Qn9He7I=
Sender: Emmanuel Lecharny <elecharny@gmail.com>
Message-ID: <49D3A0BC.20002@nextury.com>
Date: Wed, 01 Apr 2009 19:13:32 +0200
From: Emmanuel Lecharny <elecharny@apache.org>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [Client API] Search operation
References: <49CF4FE0.9040502@nextury.com>
	 <a32f6b020903290549u6be08f81i7ae21f8b4402c3c3@mail.gmail.com>
	 <49D3602A.7000007@nextury.com>
 <a32f6b020904010604sda01c83r4f69df477b15faeb@mail.gmail.com>
In-Reply-To: <a32f6b020904010604sda01c83r4f69df477b15faeb@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Alex Karasulu wrote:
> As a rule things start getting ugly with API methods when you have more than
> 4 arguments and more than 4 overloads.
>   
True.
> The most important thing to realize is what changes most with each search
> request.  The base does change most.  The filter does but sometimes does not
> need to be provided since people just want everything.  I can see something
> like:
>
> conn.search() => searches the rootDSE ? Or should this be conn.getRootDse()
> ?
>   
I would rather use a getRootDse() instead of a weird search request with 
no baseDn. So +1
> conn.search( baseDN ) => searches the base with one level scope and
> (objectClass=*)
> conn.search( baseDN, filter )
> conn.search( baseDN, filter, scope )
>   
We can add those three methods.
> Attributes and size/time limits might be best left to be overridden in the
> SearchRequest? 
I think that the Attributes should be the forth param. Anything else 
should be handled using a SearchRequest object.

> However these parameters should be set to some smart default
> when using the signatures above.  For example the sizeLimit may default to
> 1000 entries.
>   
Exactly.
> NOTE: timeLimit != timeout where the timeLimit is the limit for a search
> operation on the server, and the timeout is the time the client will wait at
> most for any operation to complete before disconnecting/abandoning the
> client request.
>   
TimeLimit is handled by the server, not the client. So yes, they are 
different values. We should have a default timeout value on the client, 
stored into the connection though.
> Also I was wondering how the Cursor interface fits into this.  Right now we
> used the DirectoryListener.
>   
Man, it fits just fine :) You have to see it...

-- 
--
cordialement, regards,
Emmanuel L�charny
www.iktek.com
directory.apache.org