Joe Larabell wrote:
|> 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.
Store the same resource in a myriad of different formats?
Not the same file... different files that make up the same site. Mostly to
avoid having to convert legacy files to the new scheme but also to allow
for structured-text (ie: wiki) files, static XML files, generated files,
legacy HTML files, etc to co-exist in the same directory with a seamless
user experience.
It should work fine. I did a couple of sites which handled various
documents, you just have to use things like
<FilesMatch "\.foo$">
processing instructions for converting foo docs to html...
</Files>
to handle documents of type "foo" and a different FilesMatch for
documents of say type "bar". You can also use some of AxKit's other ways
of selecting which transforms to use (stylechoosers). There are a
variety of them which can be used to select based on MIME types, media
types, root tag, etc.
---
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]
