Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 6804 invoked from network); 13 Jun 2005 13:40:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Jun 2005 13:40:48 -0000 Received: (qmail 13813 invoked by uid 500); 13 Jun 2005 13:40:47 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 13738 invoked by uid 500); 13 Jun 2005 13:40:46 -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 13697 invoked by uid 99); 13 Jun 2005 13:40:46 -0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS,URIBL_SBL X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of mboorshtein@gmail.com designates 64.233.184.202 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.202) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 13 Jun 2005 06:40:45 -0700 Received: by wproxy.gmail.com with SMTP id 55so387215wri for ; Mon, 13 Jun 2005 06:40:00 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gUIQQYz84v4hPWIxWCJEKZ4zB4DsoT3SsFZjShF6/7zcerSekTSLQBhyqjQefgBzZLh2c5vV/zuoHdADbwXQU7qc3ZM5PMfnnra/mubiEJlvLowdorizbw1BG1T1qPcdfnEdmdA+HnYIIkqSF0+yg8WFkZ75YLXG9UbgMuz15lY= Received: by 10.54.8.62 with SMTP id 62mr2795007wrh; Mon, 13 Jun 2005 06:33:20 -0700 (PDT) Received: by 10.54.138.1 with HTTP; Mon, 13 Jun 2005 06:33:20 -0700 (PDT) Message-ID: <800df639050613063362dc9eb5@mail.gmail.com> Date: Mon, 13 Jun 2005 09:33:20 -0400 From: Marc Boorshtein Reply-To: Marc Boorshtein To: Apache Directory Developers List , Trustin Lee Subject: Re: [apacheds] Nestable InterceptorChains In-Reply-To: <768dcb2e05061304491a67d5ff@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <768dcb2e050613001771aac139@mail.gmail.com> <800df639050613033670e97d73@mail.gmail.com> <768dcb2e05061304491a67d5ff@mail.gmail.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N So as in a "package" of interceptors? For instance there are 4 or 5 interceptors that are "default" interceptors, so that you could say in your configuration: server.interceptors=3Ddefault,myinterceptor1,myinterceptor2,... and default would be a pre-configured (or user configured) chain? The alternative would be server.interceptors=3Dcontrols,schema,authorization,...,myinterceptor1,myin= terceptor2,... I could see where that would be usefull when packaging several intercepts as a single unit. The default interceptors can either be hardcoded or there can be a "hardcoded.props" to store all configuration for a base system. I haven't looked on this roadmap, is there a GUI in the works? I suppose that would simplify the configuration. Marc On 6/13/05, Trustin Lee wrote: >=20 > =20 > 2005/6/13, Marc Boorshtein :=20 > > What was the original use case for nestable interceptor chains? > =20 > =20 > We could create custom interceptor which is actually a chain of > sub-interceptors.=20 > =20 > Trustin > --=20 > what we call human nature is actually human habit > -- > http://gleamynode.net/