[3] I'm aware of Sylvain's and Marc's proposal on changing
the scope of available controllers. I contacted Sylvain off-list
and the said that they want to come up with a concrete
implementation
of their proposal in the future and this should *not* influence
the release of Cocoon 2.1 as the proposed changes would only have
a small impact on the *public* interfaces.
+1 under the assumption that:
- we can reasonably expect that Sylvain & Marc will try to minimize the impact on public interfaces (i.e. sitemap syntax and friends) of their planned future contributions
- the 'original flow' is considered to be but one implementation of the aspect of flow handling in Cocoon, especially in the naming sense. It should be possible that sitemap constructs can be reconsidered, and it should also be possible that 'Flow' is considered to be a generalized service in Cocoon, with a number of realisations, without the 'original flow' claiming the entire Flow concept thought- and namespace
It's good to see progress in this matter, thank you for shepherding the discussion into a vote, Reinhard!
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
