joshua at chamas
May 28, 2001, 4:43 PM
Post #1 of 1
(1065 views)
Permalink
|
Hey,
Please respond with any comments on the following...
I'm creating a $Server->XSLT() method which will be called like:
my $xslt_data_ref = $Server->XSLT($xsl_data_ref, $xml_data_ref);
This will make available the same functionality that Apache::ASP uses
internally in 2.11 ( not yet released ) for handling the XSLT config,
and could be used by the developer to easily create XSLT rendered
components in an existing ASP framework.
In the future, I imagine the args to XSLT() can also be file
names that will be read in on the fly. These file names might
be treated as includes, so that they might be found in
., Global, or IncludesDir
The nice thing about this API, is that by default it will
render with XML::XSLT, but if PerlSetVar XSLTParser is set
to XML::Sablotron, it can use that too. In benchmarks just
run on the ./site/eg/xslt.xml example, I found that with XML::XSLT
I got 6 hits / sec, but with XML::Sablotron I got 57 hits / sec.
In the future, when there is a local file caching API to leverage
off of, an XSLTCache setting would start to use it for further
performance increases. Also, XSLTCacheSize will not be supported
as of 2.11 ... it was a bad implementation of a XSLT cache that used
Tie::Cache, and would produce a low cache hit ratio.
-- Josh
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks <- Web Link Checking Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
---------------------------------------------------------------------
To unsubscribe, e-mail: asp-unsubscribe [at] perl
For additional commands, e-mail: asp-help [at] perl
|
