From dev-return-21501-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Fri Sep 21 17:57:15 2007 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 57369 invoked from network); 21 Sep 2007 17:57:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Sep 2007 17:57:14 -0000 Received: (qmail 6997 invoked by uid 500); 21 Sep 2007 17:57:04 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 6951 invoked by uid 500); 21 Sep 2007 17:57:04 -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 6940 invoked by uid 99); 21 Sep 2007 17:57:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 10:57:04 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.198.186 as permitted sender) Received: from [209.85.198.186] (HELO rv-out-0910.google.com) (209.85.198.186) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 17:57:04 +0000 Received: by rv-out-0910.google.com with SMTP id g11so727742rvb for ; Fri, 21 Sep 2007 10:56:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=jRKzOLhF/ufVCdz5tDH+VoXsOdkzcNVHfV5VDcoKiY4=; b=Pd+fP8vVRkSDh/VOWCzztCyCga1eRZ4rsDMaOtB30CoP/QVkHCZ/zG+thKeoWoH+fDrkqFravEjhdpYkIXzTGkTAZCy5cTCi0uM/jUcbXzakTcugXMrz6Rhfp/Quxp3e1oALkMxnCneoanHqEXhQJvxagWiifojklrWQkpEs8wA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=qs/Q+rrxvNmolsEJSKbHD6PIk38Qp9h+Ov4LYTTWEdGclQqd39pnoqFT8hs8LNFz4cMHjTAEqvZGMh9AplhbHVZYL9noPlHbFJVgzJSzmF9vOmO4EQ+9Y4ybDZHre9yXWLELud18EmILvHQWCMRVNbJsiarwpSwiHbu+ryOEQVc= Received: by 10.115.77.1 with SMTP id e1mr3499460wal.1190397399965; Fri, 21 Sep 2007 10:56:39 -0700 (PDT) Received: by 10.115.76.8 with HTTP; Fri, 21 Sep 2007 10:56:39 -0700 (PDT) Message-ID: Date: Fri, 21 Sep 2007 13:56:39 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: [ApacheDS] Specifying application level subtrees? In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_31456_17718342.1190397399941" References: <800df6390709211011q5bdef748xcc628ccee0029829@mail.gmail.com> X-Google-Sender-Auth: 99a358143629dad7 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_31456_17718342.1190397399941 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ok got another idea on the matter ... Let's think about the inverse. You have this subtreeSelector and when you read the entry of that objectClass with object (base) scope without any controls you can get the following results: (1) a single entry with all the member attribute values injected into it (2) multiple entries if the member attribute values exceed a certain threshold If a management control is present then you see the entry without any of the magic going on. Now perhaps we need to make the subtreeSelector an AUXILIARY objectClass so it can be added to static groups. Once that happens the injection is handled by the server and clients see a static group with all it's members. Also we will need a threshold parameter in the subtreeSelector to be used as the trigger to switch from mode 1 to mode 2 based on the size of the result set. WDYT? Alex ------=_Part_31456_17718342.1190397399941 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ok got another idea on the matter ...

Let's think about the inverse.  You have this subtreeSelector and when you read the entry
of that objectClass with object (base) scope without any controls you can get the following
results:

(1) a single entry with all the member attribute values injected into it
(2) multiple entries if the member attribute values exceed a certain threshold

If a management control is present then you see the entry without any of the magic going
on. 

Now perhaps we need to make the subtreeSelector an AUXILIARY objectClass so it can
be added to static groups.  Once that happens the injection is handled by the server and
clients see a static group with all it's members.

Also we will need a threshold parameter in the subtreeSelector to be used as the trigger
to switch from mode 1 to mode 2 based on the size of the result set.

WDYT?

Alex

------=_Part_31456_17718342.1190397399941--