>
> Yeah that will be really cool... can you inform me about the progress on
> this, if you made something ... I thought about something similar
> not exact but
> some sort of processor to handle XML(XSLT) -> HTML conversations +
> some sort of caching tehnique, but I also like this
> approach
On Tue, 25 Apr 2000, Leslie Mikesell wrote:
> According to Matt Sergeant:
>
> > In case you missed it - I just announce the Apache XML Delivery Toolkit to
> > both the modperl list and the Perl-XML list. With it you can develop an
> > XSLT Apache module in 13 lines of code (no caching, but it wo
According to Matt Sergeant:
> In case you missed it - I just announce the Apache XML Delivery Toolkit to
> both the modperl list and the Perl-XML list. With it you can develop an
> XSLT Apache module in 13 lines of code (no caching, but it works).
I saw it, but perhaps misinterpreted the 'not' i
On Tue, 25 Apr 2000, raptor wrote:
> Yeah that will be really cool... can you inform me about the progress on
> this, if you made something ... I thought about something similar not exact but
> some sort of processor to handle XML(XSLT) -> HTML conversations +
> some sort of caching tehnique, but
Yeah that will be really cool... can you inform me about the progress on
this, if you made something ... I thought about something similar not exact but
some sort of processor to handle XML(XSLT) -> HTML conversations +
some sort of caching tehnique, but I also like this approachsomething like
I've just thought of a really cool idea, that would be rather easy to
implement...
First of all, when someone requests an XML document, it looks for the
processing instruction, according to the w3c
specs. We parse the "type" attribute and get:
text/xsl
or
notxslt
or
Apache::MyPageProcessor
i.e
