Re: xslcache extension

Christian Stocker wrote:

On 29.5.2009 9:13 Uhr, Alexey Zakhlestin wrote:

On Thu, May 28, 2009 at 2:57 PM, Rob Richards <rrichards@cdatazone.org> wrote:

    
Someone had asked me last week at php|tek about xsl caching and we had

tossed around the idea of possibly integrating either this or some of the fastxsl code into ext/xsl. There are some issues doing this, which were always the hold up moving on this, so the thought was to make it a compile time option disabled by default. Wanted to float the idea to Christian first though.

well, we still can do "merging" after importing code in PECL, right?

Sure, I'd even recommend to get ext/xsl and xslcache in-sync/merged in that pecl branch and then maybe sync back to the "main" branch. We have a much better idea then, what it will be and can decide how we should proceed with ext/xsl and what approach we take.

We won't be able to do the merge in 5.3 anyway

right :) chregu That works for me. Just makes sense that in the long run we aren't trying to maintain and keep in sync two xsl extensions. It's bad enough that we are currently working across 3 branches. As for the enabling if/when it gets merged into main branch, I would only be agreeable to the compile time flag. Due to the nature of this code, it needs to be much harder to enable than switching an ini setting. Rob