A Provider can provide the XSL as well. get_styles will be called to find out which stylesheets to apply, but then get_strref will be called to fetch the XSL itself.
Excellent. Thanks for that information.
Since a provider will be getting called to fetch the XSL, the href is really just an argument to the provider, and does not need to map to a file on disk. Just make sure that if your href is '/foo/bar.xsl', that your configuration points AxKit at your provider for that href. Otherwise the default provider (File) will be called.
The next thing I am concerned with is avoiding turning a XML::LibXML::Document into a string only to then parse that string back into an object. AxKit::Provider::DOM seems to use $r->pnotes('dom_tree') to pass a DOM object about, although I don't understand why A::P::DOM::get_strref() _also_ calls $dom_tree->toString() when something like AxKit::XSP::handler() seems to look for the existence of $r->pnotes('dom_tree').
I don't know whether I am confusing myself by reading various bits of code without fulling understanding the process. Is there a HowTo describing how to provide XSL as a compiled DOM instead of a string?
/dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
