Andreas Hartmann wrote:
This is a valid concern. I'm -1 on restricting the URL space. It should be possible to mimic an existing URL space when a site is migrated to Lenya. Maybe we can add a mechanism to make URL space and usecases orthogonal, for instance to map URLs to usecases ...
rather than add this feature to lenya, how about generating a .htaccess file with the necessary mod_rewrite instructions? for those who need it, they would then use that .htaccess in their frontend apache
I agree that it would be great to use the usecase concept (or even framework) to implement the search functionality. Just a random thought: Maybe we could require a hook / callback which is provided by a publication and generates the page (navigation components etc.) so that usecases can be embedded in pages?
that would make lots of sense, presumably also for portal scenarios
That would be a good place to start, because it can add significant performance boost (Xalan -> XSLTC sometimes up to 50%) and (theoretically) doesn't require changes to the code.
now that xalan 2.7.0 is out, an adventurous soul could try again.. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
