-
1. Re: Persistence/Caching interceptors
starksm64 Aug 29, 2005 12:29 PM (in response to ovidiu.feodorov)Its important to consider whether or not the aop framework can be plugged into any service component. What can be externalized/customized via an interceptor/advise on a call path is something we need to consider if we are going to get max reuse of both existing aspects as well as the extensibility to allow for customization.
-
2. Re: Persistence/Caching interceptors
ovidiu.feodorov Aug 29, 2005 12:38 PM (in response to ovidiu.feodorov)We are already using AOP and we have a server-side AOP interceptor chain, which contains interceptors like SecurityInterceptor and InstanceInterceptor. So the framework to allow us to externalize aspects is there. I raised this issue because persistence/caching naturally belongs to an interceptor, and the current architecture doesn't allow me to do that easily, which is probably a hint that I have to change it.
-
3. Re: Persistence/Caching interceptors
starksm64 Aug 29, 2005 12:53 PM (in response to ovidiu.feodorov)Right, I would agree. I'm just pointing out that the first thing to consider is whether a given subsystem will lend its self to aop type of customizations. If it does not to some extent there needs to be a very strong performance/security type of reason.