Hi, We're currently evaluating AxKit for use on our company's website and we are having good success with it, but I have one question.
We would like to keep all the site's content in XML files, and transform them into XHTML using XSLT. I would also like to add extra variables before the XML is transformed into XHTML. I'm trying to do this without using a language that embeds perl code inside the XML or XSLT. I had planned on writing a Provider module that pulls information from a database and cookies, etc, then set it up to inherit from Apache::AxKit::Provider::File. It would modify the XML content stream and add extra, or set existing, parameters in the XML before being transformed. IMHO, this is not too elegant, but this is a starting point I am fairly certain I can get to work. Another thing we have tried, with good success is feed the XML output of an Apache::RegistryFilter script into AxKit, and have it apply XSLT to produce HTML. We could use the same approach and make a handler load the XML, add the parameters then have it feed the completed doc to AxKit. I'm also confident this will work, but not optimal because I'm trying to get AxKit to do most of the work for efficiency reasons (both programmer and in the program code) and ideally want just focus on the logic. My main goal is to seperate content, presentation and logic into XML, XSLT, and perl modules, repectively. I am sure that someone on this list has done something similar to what we are doing. Is there any recommended elegant/efficient way to do this from those that have experimented with different approaches? Thanks, Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
