Return-Path: Delivered-To: apmail-directory-api-archive@minotaur.apache.org Received: (qmail 1093 invoked from network); 4 Sep 2010 16:41:07 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Sep 2010 16:41:07 -0000 Received: (qmail 55389 invoked by uid 500); 4 Sep 2010 16:41:07 -0000 Delivered-To: apmail-directory-api-archive@directory.apache.org Received: (qmail 55350 invoked by uid 500); 4 Sep 2010 16:41:07 -0000 Mailing-List: contact api-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: api@directory.apache.org Delivered-To: mailing list api@directory.apache.org Received: (qmail 55339 invoked by uid 99); 4 Sep 2010 16:41:07 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Sep 2010 16:41:07 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.178] (HELO mail-iw0-f178.google.com) (209.85.214.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Sep 2010 16:40:44 +0000 Received: by iwn35 with SMTP id 35so3417622iwn.37 for ; Sat, 04 Sep 2010 09:40:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.17.11 with SMTP id q11mr3076655iba.63.1283618422182; Sat, 04 Sep 2010 09:40:22 -0700 (PDT) Sender: mail@stefan-seelmann.de Received: by 10.231.13.73 with HTTP; Sat, 4 Sep 2010 09:40:22 -0700 (PDT) Date: Sat, 4 Sep 2010 18:40:22 +0200 X-Google-Sender-Auth: qvA3RA2rsdLgiDUNtz0rLNoRgPw Message-ID: Subject: Different layers From: Stefan Seelmann To: api@directory.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Hi guys, in IRC we had the idea to have different levels of abstraction in the API: A low-level API that represents the LDAP protocol and a more convenient API for common users that hides the LDAP complexity. Lets start with the search method. In the low-level API the search method would return a Cursor and the user has to deal with all possible results (SearchResultDone, SearchResultEntry, SearchResultReference, IntermediateResponse) In the convenient API the search method would return a Cursor and the search method could also deal with referrals and search continuations (throw as exception or follow transparently if the user wants to). Does that make sense? This is just a first thought, we have to figure if it makes also sense for the other operations too. Kind Regards, Stefan