On Mon, 21 Jul 2003, Sam Tregar wrote: > My impression is that Mason doesn't get much advantage from clients > that only use part of the Mason system. I imagine that one of the > reasons that the Mason workalike I built for Bricolage is faster than > Mason is that it only implements the functionality actually needed by > Bricolage. Following this line of thinking it might be possible to > modify Mason to only use/load the slower/bigger pieces when they are > actually needed. Of course, I'm no authority on why Mason is slow or > how it could be fixed.
It's not the loading of things that's slow, it's the execution path for a request. We do have some ideas on how we can speed this up, but it'll probably involve the user choosing an optimized, less feature-ful or flexible class for something (like resolving URLs to components), rather than Mason itself trying to figure out what to optimize dynamically. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
