Daniel Fagerstrom wrote:
Reinhard Poetz skrev:
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"/>
Is anybody working on this right now or in the foreseeable future?
The core split, springification of components and stabilizing the blocks
fw are higher on my personal priority list. I'll help, if you (or
someone else) start working on it.
Unfortunatly it isn't on the top of my todo list either. Over the next weeks I
will concentrate on the documentation and the release of some more blocks.
I consider the service components very useful for some more sophisticated block
usage scenarios. Hopefully somebody else has more time :-)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
