On Thursday, Aug 14, 2003, at 14:22 Europe/Rome, Sylvain Wallez wrote:
Jeff Turner wrote:
<snip/>
Isn't the problem there that a <map:read> is a whole little pipeline unto itself? If it were broken into two atomic operations:
<map:generate type="binary" src="foo.doc"/> <map:serialize type="binary"/>
then we could have a <map:view from-position="first"/> using a content-aware pipeline, and everything would work.
I have the feeling that handling non-XML content in Cocoon is Just Wrong, and that <map:read> is just a hack. The fact that it doesn't integrate with Views is a symptom of this. In a theoretically pure world, we'd either make Cocoon an XML-only framework and kill <map:read>, or make Cocoon a generic data pipelining framework capable of handling and transforming binary content.
Well it's a RT after all.. ;)
Content-aware and binary pipelines in the same post? Wow! Yes, it's definitely a RT ;-P
I am against to both content-aware selection and binary pipelines.
I still have to see a need for them that cannot be solved with machinery already in place or with the newly proposed RequestFactories.
-- Stefano.
