Re: Scheme handlers for XSLT in progress.

From: Date: Fri, 31 Oct 2003 15:19:31 +0000
Subject: Re: Scheme handlers for XSLT in progress.
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-5150@lists.php.net to get a copy of this message
Just as an update to this question According to Adam, the stream-wrapper support in ext/xsl seems to have the same possibilities as the schemes support in the former sablotron extension. But he will further look into it and keep us/me updated about the outcome ;) <extremely_shameless_plug> I will talk about stream-wrapper support in ext/dom and ext/xsl in my talk next week at the php conference (and in the slides/examples published afterwards) ;) </extremely_shameless_plug> chregu On 10/31/03 12:20 PM, Adam Dickmeiss wrote:
Christian Stocker wrote:
On 10/31/03 11:23 AM, Adam Dickmeiss wrote:
Hi, we miss the scheme facility from PHP4's XSLT extension. So, we are making a new one for PHP5's XSL extension, i.e. interfacing libXSLT's xsltRegisterExtModuleFunction. If nobody else have done it/is doing it we'd like to contribute.
Can't you just use the stream-wrappers provided by PHP5? These are very well supported even in xslt. What's the difference between them and the sablotron way? Besides the different API in PHP userland? chregu
Don't know the stream-wrappers, but from what I can see it doesn't do what we need. We want to be called by XSLT (with args etc) when XSLT meets registered elements&NS. So if you want a stylesheet with side effects, say that search in a database, just chaning the stream of XML doesn't help. XSLT must be in control - must have processed the args to the handler A stream approach is "separate" pass. Again, I may have misunderstood something, so we'd really like to know if it can be achived already.. -- Adam
-- christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 1 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | chregu@bitflux.ch | gnupg-keyid 0x5CE1DECB

« previous php.internals (#5150) next »