cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Haul <>
Subject Re: [SUMMARY] input module chaining
Date Wed, 09 Oct 2002 16:55:19 GMT
On 09.Oct.2002 -- 08:54 AM, Carsten Ziegeler wrote:
> Ok, I think the first sentence here is one central point of problem:
> Currently I (and it seems others as well) see input modules only as
> components
> to be used in the sitemap.
> I think Christian had a much wider intention for this concept.
> If we use InputModule primary in the sitemap than this is a "special"
> Cocoon concept - if this has a much wider sense than InputModules should
> be more general and shouldn't be developed inside Cocoon but
> for example Excalibur or Commons etc.
> That's the reason why I didn't answer the question where OutputModules
> or the third one should go - I think all of this does not directly
> belong to Cocoon because it has a more general approach.

Carsten, sorry for answering late.
OK, so what further course of action would you suggest? Post a
description to avalon-dev and ask for an opinion?

C h r i s t i a n       H a u l
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

To unsubscribe, e-mail:
For additional commands, email:

View raw message