Lists Home |
Date Index |
Peter Hunsberger wrote:
> The guts of Cocoon use a SAX stream "compiler"; it captures the SAX
> events for latter replay. Haven't really looked, but I suspect it
> could almost be used standalone...
But, whenever you do a transformation, those SAX events need to be
converted to the XSL processors internal DOM - a parse.
> Yeah, but I thought we already figured out how to avoid the parsing...
>>>Finally, have you looked at any of the various Cocoon templating
>>>solutions (which includes Velocity)?
>>What? You don't remember me from the cocoon lists? :)
> Yes, that's why I was asking: did you consider them and reject them,
> or is this not a Cocoon project, or ???
I think cocoon is a cool project. The way our CMS works does not lend
itself to recieve the benefits cocoon would offer. And, don't know if
you recall, but I had fundamental disagreement with regard to the
document function. I use the document function quite a bit and, unless
it has changed, cocoon tended to discourage its use.