Chris is right (except it's not introspecting the filters since filters only have one event other than the configure that Mach-II can run). Mach-II looks for which plugin points that are implemented and only calls inplemented points (like preEvent, postEvent, but none of the others etc.).
Sounds like you are worried about start up time during developement. I usually leave the config_mode set to -1 and have a url param like reloadApp that can reload the whole application when needed. What are you usual load times on Mach-II in seconds?
Best,
.Peter
P.s. If this goes much too much, we should probably move this to the Mach-II list where we can continue the conversation.
From: Chris Scott <[EMAIL PROTECTED]>
Sent: Tuesday, March 14, 2006 7:48 PM
To: [email protected]
Subject: [coldspring-dev] Do I understand this correctly?
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.
- [coldspring-dev] Do I understand this correctly? Troy Simpson
- [coldspring-dev] Do I understand this correctly? Chris Scott
- [coldspring-dev] Do I understand this correctly? Troy Simpson
- [coldspring-dev] Do I understand this correctly? Troy Simpson
- [coldspring-dev] Do I understand this correctly? Chris Scott
- [coldspring-dev] Do I understand this correctly? Chris Scott
- [coldspring-dev] Do I understand this correctly? Chris Scott
- [coldspring-dev] Do I understand this correctly? Peter J . Farrell
- [coldspring-dev] Do I understand this correctly? Kurt Wiersma
- [coldspring-dev] Do I understand this correctly? Kurt Wiersma
- [coldspring-dev] Do I understand this correctly? Kurt Wiersma
