directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Boorshtein <mboorsht...@gmail.com>
Subject Re: [apacheds] Nestable InterceptorChains
Date Mon, 13 Jun 2005 13:58:34 GMT
Think it sounds like a great idea.  What would the property config
look like?  I would suggest something similar to the partition config
pattern (though I wouldn't have the interceptor specific properties in
an external properties file).

Marc


On 6/13/05, Trustin Lee <trustin@gmail.com> wrote:
> The complexity of interceptor chain comes when we interpret the word
> 'nested' as nested.  Let's assume that there are two interceptor chains in
> top level chain.  When we are using the word 'nested', it means something
> hierarchical.  So we can simply assume they are packaged like one
> interceptor and works as a unit.  But it is not true.  They are expanded
> like this: 
>   
> A -> A1 -> A2 -> B -> B1 -> B2 -> B3 
>   
> A and B are interceptor chains and Ax and By are their childrens.  Hierarchy
> has no meaning here actually like above. 
>   
> The most significant problem is to decide whether the nested chain is
> interpreted as a chain, and therefore can work as 'before' and 'after'
> pointcut.  For example, if you added chain A as a 'after' pointcut, here is
> new execution order: 
>   
> A -> B -> B1 -> B2 -> B3 -> A1 -> A2 
>   
> This completly breaks the meaning of 'nested', so it brings a lot of
> complication.  They are not nested actually, and makes the execution order
> complicated. 
>   
> Instead we could add a set of interceptors as a set of
> InterceptorConfigurations. Here is the example: 
>   
> MutableStartupConfiguration cfg = new MutableStartupConfiguration(); 
>   
> Set interceptorSet = GroupedInterceptor.INTERCEPTOR_SET; 
>   
> cfg.setInterceptors( cfg.getInterceptord().addAll(interceptorSet) ); 
>   
> WDYT? 
>   
> 2005/6/13, Marc Boorshtein <mboorshtein@gmail.com>: 
> > 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=default,myinterceptor1,myinterceptor2,...
> > 
> > and default would be a pre-configured (or user configured) chain?  The
> > alternative would be
> > 
> > server.interceptors=controls
> ,schema,authorization,...,myinterceptor1,myinterceptor2,...
> > 
> > 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.
>  
>   
> There's no GUI works yet.  I'm working on making ApacheDS configurable
> easily via Spring Framework. 
>   
> Trustin 
> -- 
> what we call human nature is actually human habit
> --
> http://gleamynode.net/

Mime
View raw message