Hi guys. > Imagine having an XSL processor in the kernel: I don't think you are asking for xsl in the kernel. What you are asking for is the cocoon shell: cocoonsh. Also, though it would be theoretically possible to implement an xml aware filesystem-- Some experience (google search xdelta xdfs) has shown that a usermode filesystem extension (i.e. cocoonfs) may be more convenient. And if you want that mapped to a mountable filesystem in linux, use a thing like podfuk <http://uservfs.sourceforge.net/>.
The most useful thing the coda project has come up with is a simple filesystem hook into linux: /dev/coda. Podfuk is a great usecase. The possibilities are amazing. Tim > 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. > > Tony >
