Oh wait, sorry I didn't get what you said the first time I read it.
No I don't think Mach-ii works like that at all. When Mach-ii loads
itself up, it looks through all the plugins and filters to see what
methods it can call on each object, so when it goes to call
preProcess for instance, it already knows which plugins it can call.
It would be pretty inefficient to do that at run time.
On Mar 14, 2006, at 9:46 PM, Chris Scott wrote:
On Mar 14, 2006, at 9:29 PM, Troy Simpson wrote:
This question is mostly out of curiosity.
Is mach-ii inspecting the ColdSpring plugin for methods that have not
been overriden like the pre- and post- methods with each page
request?
Does this add much overhead to each request?
Huh? Other way around. ColdSpring inspects your Mach-ii components.
And only during application startup. If you autowire everything
when your app startups, ColdSpring pretty much sits around in the
bar drinking while your app runs. Unless you are using AOP that is,
then it bosses around your methods, but that's another story...
