Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 88683 invoked by uid 500); 15 Jul 2003 20:50:39 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 88603 invoked from network); 15 Jul 2003 20:50:38 -0000 Received: from www.plenix.com (HELO www.plenix.org) (65.222.219.21) by daedalus.apache.org with SMTP; 15 Jul 2003 20:50:38 -0000 Received: from apache.org (quito.plenix.org [66.198.46.82]) by www.plenix.org (8.12.3/8.12.1) with ESMTP id h6FKofhN007799 for ; Tue, 15 Jul 2003 13:50:43 -0700 Date: Tue, 15 Jul 2003 15:52:39 -0500 Subject: Re: [RT] The perfect repository might be just under your eyes Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Stefano Mazzocchi To: dev@cocoon.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <3F1466A0.5080304@umn.edu> Message-Id: <45B31CE8-B706-11D7-A769-000393D2CB02@apache.org> X-Mailer: Apple Mail (2.552) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tuesday, Jul 15, 2003, at 15:40 America/Guayaquil, Tony Collen wrote: > More RTing: > > Imagine having an XSL processor in the kernel: > > You could "execute" .xsl files, bypassing having to run a processor > manually. > > prompt$ page2html.xsl < input.xml > output.html > > Borrowing the pipeline concept from Cocoon: > > prompt$ cat input.xml | page2foo.xsl | foo2bar.xsl | bar2html.xsl > > output.html > > One could even invent files which are actually transformation > pipelines -- ones which you might not be able to directly edit (or > maybe be able to edit a transformation in the middle): > > prompt$ make-virtual-file-pipeline virtual.xml --generator=input.xml > --tranformers=page2foo.xsl;foo2html.xsl --serialize=text/xml > > Now you can just go > > prompt$ cat virtual.xml > > And get the output of the pipeline defined above, which you can then > link to other pipelines, etc. > > It's no wonder that this all fits in very well with what Cocoon does, > since Cocoon is patterned after this concept. I'm sure if I stew on > this concept enough I'll come up with more ideas and uses. It might be a good mental exercise, but before you do, please remember that UNIX has no notion of structured pipelines as Cocoon does. That is, you will always need a serialization/parsing stage between different filters, which is instrinsically poor. Also, consider that there is no type safety since all components are the same (unlike in cocoon where you can't have a transformer after a serializer). So, keep in mind the differences. -- Stefano.