Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 94331 invoked by uid 500); 21 Feb 2002 13:57:11 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 94320 invoked from network); 21 Feb 2002 13:57:11 -0000 From: "Vadim Gritsenko" To: Subject: RE: is cocoon symmetry a holy grail? Date: Thu, 21 Feb 2002 08:55:15 -0500 Message-ID: <006201c1badf$63a4e9b0$90a4558b@vgritsenkopc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Torsten Curdt [mailto:tcurdt@dff.st] > > On Thu, 21 Feb 2002, Vadim Gritsenko wrote: > > > > From: Torsten Curdt [mailto:tcurdt@dff.st] > > > > > > Did I get you guys right? You want to merge XML streams? > > > > Split, pass through several pipelines, and merge together. > > > > > > > Merging XML is a tough one... > > > > Not (much) tougher than CIncludeTransformer and ContentAggegator :) > > Well, our CA is currently not really merging but including parts into a > new document. I though that's the difference: merging instead of > including. If not - I didn't get the difference to CA correctly... Difference between CA and thing proposed is that in CA map:part decides where from it gets XML, and in this proposal "multiplexer" streams SAX events to the sub-pipelines, replacing generator defined in the sitemap. Hence the picture: split, feed to several pipelines, and merge results. Vadim > -- > Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org