Hi!
Michael Kröll wrote:
Peter Mueller wrote:
The AxKit man pages and the book clearly say any ONE of
get_strref, get_dom or get_fh must be implemented, so why
is AxKit insiting on get_strref if get_dom is available ?
Sounds like a (documentation) bug.
So get_strref has to be there, even if get_dom or get_fh are implemented ?
Is there a way to do it with get_dom and without get_strref?
Since get_strref() is called before get_dom(), I store the parsed DOM
object in $self during get_strref() and access it from get_dom() as a
workaround.
That's similar to my solution. I build my DOM tree in the process method,
and store it in self.
get_dom returns this reference and get_strref uses toString at the first
use, and stores the string in self too to make later calls more efficient.
So the question is - how "expensive" is LibXMLs toString ?
I didnt do profiling on the perl code until now.
Is there a significant performance change if the XSL transformation called
as the next stage after my custom provider uses get_dom instead of
get_strref ?
Is there a chance to make the stylesheet evaluation code of AxKit use
get_dom
and would this be a sigificant performance boost compared to get_strref ?
Maybe the gurus using AxKit on heavy loaded productions systems can
bring some light into this - I am developing an interactive web-Interface
and at the moment there is no easy way to make comparable perfomance
tests so I am just guessing where to tweak out the speed ...
There have been a few changes to the provider code in CVS IIRC, but not
that I remember that behaviour being fixed.
Maybe I should try the recent CVS ...
Maybe someone fix that, change the documentation, or tell us what we are
doing wrong?
Would be nice if someone involved in this could give me a hint if its my
poor programming or misunderstanding of AxKit or if it is as it is ...
Bye, Peter
WOTLmade
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
