Return-Path: 
 <cocoon-dev-return-25573-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 98891 invoked by uid 500); 11 Apr 2002 19:33:07 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 98874 invoked from network); 11 Apr 2002 19:33:07 -0000
Date: Thu, 11 Apr 2002 15:32:51 -0400
Subject: Re: XSLT 2.0 and Pipelines
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v481)
From: Jason Foster <jafoster@uwaterloo.ca>
To: cocoon-dev@xml.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <3CB5DBA0.5090107@anyware-tech.com>
Message-Id: <E9C37019-4D82-11D6-A3D4-000A27E14D02@uwaterloo.ca>
X-Mailer: Apple Mail (2.481)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

<snip/>

> Every URI in Cocoon gets resolved to a Source object, and we have some 
> WriteableSources. So xsl:result-document will naturally go to any 
> WriteableSource !

Isn't this basically like that multiplexer idea that has been floating 
around?  We can now have one transformer that spits out multiple results, 
each of which can be a source for another pipeline.  Based on this, isn't 
it necessary for Cocoon to introduce multiplexers?  Either that or we have 
to tell the XSLT authors not to use a standard feature of their technology.

Jason Foster


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