Andreas Hartmann wrote: > Andreas Hartmann schrieb: > I did some more tests - maybe I did missed something before, but now I > get different results which resemble my expectations. > > * same setup as above > * Lenya 2.0.2-dev without modifications > * Fallback source URI caching enabled > > a) standard publication.xml: avg. 1200 ms > b) publication.xml contains only modules with menus: avg. 800 ms > > In case b), the aggregated menu XML is cached because the include > transformer didn't come across any non-existing sources and therefore > the validity could be computed. > > At the moment b) can't be enforced because the publication.xml entries > are also used for i18n. But I'm confident that we would find another way > to assemble the modules i18n catalogue. > > WDYT - can we require that publication.xml contains only modules which > provide a menu, and throw an exception otherwise?
nah. the current situation is bad enough (having to specify modules for i18n). i think the only sensible behaviour from a user POV is either not to specify any modules at all and always activate all modules (not a good idea, but at least it's consistent), or better yet, only specify those modules we wish to use and effectively disable all others (i.e. not only their menus, but everything including usecases, menus and i18n). this might make sense for security - i.e. an old abandoned module with a critical usecase might open a security hole that no-one realizes because it's not visible. but that would imply another lookup each time a module resource is resolved... dunno how much overhead that'll cause. -- Jörn Nettingsmeier "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
