Jeremy Quinn wrote: > > During the 'put' phase in <slash-edit/>, the instance, having been > assembled from the Request by an XSLT, it is then processed with the > generated Validator XSLT. > > Next an 'adaptor' XSLT checks there were no Validation errors before > wrapping the instance in a <source:write/> tag so that the > SourceWritingTransformer (later in the pipeline) can output it to the > Source. > > Is it these tiny, one-job adaptor XSLTs and the logic they perform causing > you these problems, or is it the whole concept of incrementally adapting > content in the pipeline?
It seems to be a fairly procedural approach and, while I have not seen what these XSLT stylesheets do exactly, they appear to work in a fairly deterministic way. XSLT is not ideal for procedural algorithms, but at the end of the day it's just another language. There is a tradeoff between doing things in a less-then-ideal, but available language compared to an ideal, but less-than-available language. If you use XSLT just for two internal things, the tradeoff may be on your side, if your users start to write their own XSLT stylesheets to configure the process, then perhaps the tradeoff falls on the other side. YMMV :) cheers, Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
