Joe Larabell wrote:
Hi,
Sorry to have left such a long gap in the conversation. I'm kinda
embroiled in a bit more than I can handle right now.
In re: my earlier post on chained conversion...
Not really such a tall order...
<Files *.html>
(directives to convert your .stx to html)
</Files>
<Files *.xml>
(directives to convert your .stx to some xml dialect)
</Files>
Will the provider approach chain well? I can see that if I have a .xml
file and the user asks for a .html file, I can apply the usual XSLT to do
the conversion and return the result. If I have .stx and the user asks for
a .xml file, I can use a provider to perform the conversion. But if I only
have an .stx file (text, basically) and the user requests a .html file,
and if I have one provider that knows how to produce an .html from a .xml
and another that knows how to produce .xml from .stx, will AxKit be able
to deduce that the two conversions chained together would cause the format
I have to be converted into the file I want?
well, the original URL tells apache what the client wants for an output
format, so say in that case you could do:
<Files *.html>
(file provider to provide the .stx)
(transform to turn .stx to .xml, could also be done directly by
custom provider)
(transform to turn .xml into .html, generally an XSLT stylesheet)
</Files>
And it's not just limited to .stx -- I could have .cgi's in there as well
which would produce some .xml format and need further conversion (that I
know is already possible with AxKit because I've done it). But when the
user asks for a directory, can I force a directory dump provider to pass
XML source down the chain for conversion?
Yes, its slightly tricky and I don't recall the exact ins and outs, but
its quite doable once you get past one or two minor
configuration issues.
Since perl is behind AxKit, it
is probably 'possible' but I haven't yet seen an implementation of a
complete CMS-like system that can handle files stored in a myriad of
formats.
AxKit isn't a CMS in and of itself, but it certainly can do all the file
conversions quite handily, and there are at least
2 CMS systems built with AxKit AFAIK. I haven't used them, but the
developers will no doubt reply since they frequent this list....
I'm wondering if AxKit is better or if I should just resign
myself to rolling my own solution.
Well, as long as Apache 1.x is your platform I see no reason to go to
the work of rolling your own. Apache 2.x is still
not supported by AxKit per-se, although both myself and Tom Schindl have
both built some 'axkit-like' modules for
near-term we'll have replicated the majority of AxKit's core
functionality on Apache2. Some of the more sophisticatedApache2 that
seem to work reasonably well. Tom has 'TomKit', which you can find a D/L
for on this list in his recent posts, and I have a mod_perl output
filter that does XSLT and callback-based taglib type stuff. I think that
in the fairly taglibs are another story, though converting a provider to
Apache2 should be pretty straightforward.
---
Joseph L (Joe) Larabell Never fight with a dragon
[EMAIL PROTECTED], [EMAIL PROTECTED] for thou art crunchy
http://www.larabell.org and goest well with cheese.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
