After having dealt with AxKit for a while, I think it's cool. I have come to loathe the limitations of XSP however, and would like to take advantage of the XML-pipeline model without the fuss of dealing with XSP documents.
What I really want to know is:
Is there a way to have normal CGI scripts generate the XML (just as they would HTML or any other text for that matter) and have that XML be treated as the source in a pipeline. Oh yea, being able to define the pipeline at runtime is a huge need. Something that would let me do this:
#==================START============================================== use MagicalModuleThatDoesntExist qw/pipeline/;
push @pipeline, {href => "somefile.xsl", type="text/xsl"};
push @pipeline, {href => "someOtherfileA.xsl", type="text/xsl"} if SomeCondition();
push @pipeline, {href => "someOtherfileB.xsl", type="text/xsl"} unless SomeCondition();
print <<EOF; <DOC> <TITLE>Where Wishes Come True</TITLE> <CONTENT> EOF
print makeContent();
print <<EOF; </CONTENT> </DOC> #==================END================================================
See what I mean? It doesn't have to be just like that, I'm just using that as an example. Basically I just want to set the XML source up and then feed that to the XML pipeline. I read a little bit about that Apache::AxKit::Provider::CGI (I think that's the name) module, but it looks like it only allows you to specify one provider, and not the whole pipeline. That sucks.
Any advice would be welcome. Short of a simple solution, I'm thinking we will just move to MASON for this project. XML/Ax might be overkill.
--jim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
