Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
Yes, I think we should go through all these attributes and see/vote
which ones can be made dynamic.
IIRC, this vote was already done at Cocoon 2.0 times. Substitution for component
types etc was prohibited on the basis that it makes it easier to implement
"dynamic pipelines".
Yeah, I know - and that's absolutely ok for component types. But what
about mime-type,
or the some others Marc listed?
I think following attributes can be subject to substitution:
status-code, mime-type on serialize and read
src on act
session, global, permanent on redirect-to
and probably
pattern on match
as well.
Vadim
