Return-Path: 
 <dev-return-46327-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 54817 invoked by uid 500); 14 Aug 2003 12:22:06 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 54781 invoked from network); 14 Aug 2003 12:22:06 -0000
Received: from smtp5.wanadoo.fr (HELO mwinf0402.wanadoo.fr) (193.252.22.27)
  by daedalus.apache.org with SMTP; 14 Aug 2003 12:22:06 -0000
Received: from anyware-tech.com (AToulouse-206-1-1-212.w81-50.abo.wanadoo.fr
 [81.50.74.212])
	by mwinf0402.wanadoo.fr (SMTP Server) with ESMTP id F00698000C4
	for <dev@cocoon.apache.org>; Thu, 14 Aug 2003 14:22:05 +0200 (CEST)
Message-ID: <3F3B7EED.90004@anyware-tech.com>
Date: Thu, 14 Aug 2003 14:22:05 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: fr, en, en-us
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [RT] Views for readers
References: <3F3A0C9C.3090003@anyware-tech.com>
 <20030814113802.GA4824@expresso.localdomain>
 <3F3B7583.1010403@anyware-tech.com>
 <20030814121741.GA420@expresso.localdomain>
In-Reply-To: <20030814121741.GA420@expresso.localdomain>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance  -  http://www.orixo.com