Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3E4799D8.8030704@apache.org>
Date: Mon, 10 Feb 2003 14:23:52 +0200
From: Neeme Praks <neeme@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; et-EE;
 rv:1.2.1) Gecko/20021130
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Cc: Andreas Hochsteger <andreas.hochsteger@oeamtc.at>,
	Andreas Hochsteger <e9625392@student.tuwien.ac.at>
Subject: Re: [PROPOSAL] Cocoon Science Fiction
References: <200302092147.51460.e9625392@student.tuwien.ac.at>
 <3E4794AB.9020603@apache.org>
In-Reply-To: <3E4794AB.9020603@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


I agree with Stefano on his point that if this kind of machinery is to 
be done, then it should not be done inside cocoon.
Instead, it would be much more sensible to do this on a more general 
level: write an Avalon based server for dealing with any data type where 
it would be possible to plug in Cocoon "block" as well.
Then you could have a block interface like this:
	serialized data -> block -> serialized data
And Cocoon could be just one of the many implementations for this.

Rgds,
Neeme

Stefano Mazzocchi wrote:
[..snip...]


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