--On Friday, March 19, 2004 5:11 PM +0000 Dave Roe <[EMAIL PROTECTED]> wrote:
This Provider will be responsible for providing the XML (looks simple enough to handle this using get_strref()), but providing the dynamic XSL looks tricky.
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. The tricky part is avoiding having AxKit cache the XSL from a previous request, but disabling caching should do the trick. I think AxKit will still cache the href of the XSL to use, but not the contents. (Though I think I sent Matt a patch for that, so it wouldn't cache the get_styles results either if caching is disabled, but I dont know if it ever got integrated.)
You might be able to leave AxKit caching on, and always provide a timestamp (via the mtime() method) for the XSL that indicates the XSL needs to be refreshed, but multiple queries per second might cause you problems.
It seems to me that what I want to be able to do is handle the call to get_styles(), returning one or more entries like the above except href => 'file_on_disk' would be replaced with, ideally, the XML::LibXML::Document I have created that contains the dynamic XSL. Is there an alternative to href that will do that, or perhaps an axkit: URI?
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.
-David
David Nolan <*> [EMAIL PROTECTED]
curses: May you be forced to grep the termcap of an unclean yacc while
a herd of rogue emacs fsck your troff and vgrind your pathalias!--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
