cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Ng" <stephen...@lumigent.com>
Subject RE: [PROPOSAL] Remove SQLTransformer in 2.1
Date Mon, 15 Jul 2002 13:31:01 GMT
> second:
> I don't want to rain on your parade, but...
> from an architectural point of view: is 
> "resolver.resolve("cocoon://dynamic-sql")" in XSP so much 
> better than "document()" in XSLT ?
> 
> Yes, the first is cached, and I agree (up to a point, though) 
> that SQL queries belong to generation rather than 
> transformation, but this resolver breaks the beauty of the 
> sitemapm: having all pipelines pieces in one place.
> 

It *is* cached, and (more important to me), I have a great deal of
control over the caching mechanism....  To get the same kind of control
with a transformer I have to subclass the transformer, which is (I
think) more work.

--Steve

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message