Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <4541142D.2070103@reverycodes.com>
Date: Thu, 26 Oct 2006 16:01:49 -0400
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Postable block protocol
References: <32438240.1161770236540.JavaMail.root@brutus>
 <453F4CFC.4000307@nada.kth.se> <ehnnrh$es1$1@sea.gmane.org>
 <453FB155.9080703@nada.kth.se>
In-Reply-To: <453FB155.9080703@nada.kth.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Daniel Fagerstrom wrote:
> What I would propose is to create some new pipeline components that 
> calls postable sources, and make the block protocol postable. Then we 
> have four cases for the different combinations of XML or non XML input 
> and output respectably:
> 
> non XML -> non XML
> <map:read type="service" src="block:b:/foo1"/>
> 
> non XML -> XML
> <map:generate type="service" src="input.txt">
>   <map:parameter name="service" value="block:b:/foo2"/>
> </map:generate>
> 
> XML -> XML
> <map:transform type="service" src="block:b:/foo3"/>
> 
> XML -> non XML
> <map:serialize type="service" src="block:b:/foo4"/>

It took me at least 5 min to understand what you mean... So I want to confirm 
that I got it right. :)

Do you mean that proposed "service" Reader / Generator / Transformer will 
resolve the Source object passed to it and will try to "forward" post body (if 
any) of the current Request into that Source?

Do I get it right that you are proposing to introduce new PostableSource interface?

And WRT to ModifiableSource, I do not think it is a good match here. 
Semantically, good old Source.getInputStream() corresponds to GET, 
ModifiableSource.getOutputStream() corresponds to PUT, so it looks like 
'postable' source should not be using ModifiableSource but introduce its own 
interface.

Vadim