cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conal Tuohy" <con...@paradise.net.nz>
Subject overloading sitemap variable names
Date Sun, 13 Oct 2002 22:16:46 GMT
> -----Original Message-----
> From: Geoff Howard [mailto:cocoongeoff@yahoo.com]

> How would this name overloading work with respect to:
> - references from resources back to their calling
> pipeline
> - from a subsitemap back to the mounting reference
>
> Seems these cases may make overloading desireable.
>
> Geoff Howard

I have some reservations at least about the 2nd case. I would be interested
to hear what other people think, because it seems to me that the practice of
a child block referring to named components within the parent block is a
complication worth avoiding.

It seems to me that a child block should not, as a matter of principle,
depend on its parent block containing a component with a particular
variable-name. This would complicate the interface between blocks, and make
it difficult to re-use them.

AFAIR the original plan for blocks envisaged information being passed only
in the URI, and if the child block needed access to some data from the
parent then the parent block could pass that data in the map:mount call,
avoiding a dependency on any particular name (effectively passing it as a
parameter).

Cheers

Con


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


Mime
View raw message