Jörn Nettingsmeier schrieb: > Andreas Hartmann wrote: >> Joern Nettingsmeier schrieb: >>> i think you may be a little biased against xslts... >> >> I used to like it a lot, and I still like it for certain purposes, but >> it tends to get in your way when you try to increase the performance. > > i don't really buy that argument. granted, the best way to make an xslt > fast is not to do it (again). but since menus don't change much, there's > a lot of room for optimization. i don't think menu transformations are a > performance bottleneck atm, and cocoon is all about pipeline caching.
The state of the menu items has to be computed for every request, since it depends on the AC permissions and the current state of the document. I don't think there's much to cache. [...] >> IMO XML is good for data, but not for the description of processes. > > can't see why. can you give me an example of a domain-specific language > that can't be done in XML? The question is not if it can be done, but if it is comfortable to work with. >> Our menu is a special case - it has a basic structure (which XML is >> fine for), but there's some logic to control the details. We have to >> find a way to separate these aspects, maybe by introducing a generic >> mechanism to show/hide/enable/disable menu items. > > hmm. especially for trivial things such as menu enabling/disabling, It's not really trivial - you might have to access data about the document, the current session etc. A simple example - you want to enable/disable a menu item depending on the return value of a method call. You can't do this in XSLT easily. >> XML has its fields of application. But I wouldn't like to implement >> an OS core in an XML-based language :) > > gotcha: you wouldn't want to implement an OS core in java either. :-D True, but that's not a pro-XML argument :) -- Andreas -- Andreas Hartmann, CTO BeCompany GmbH http://www.becompany.ch --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
