On Thursday, Feb 6, 2003, at 04:43 Europe/London, Alex Sergeyev wrote:
Hello,It's semi intentional. The problem is that XSP is evaled, and doesn't cache, so you're basically evalling every hit there. This would be a performance nightmare.
If I do use: XSP->XSL->XSP again
than AxKit overload XSP every time.
And after some runs it don't run first page - It thinks, that XSP was not changed and uses old version of SECOND XSP.
Joerg has plans to fix this though and to incorporate some cache management so you don't have to eval on every hit. That might be 1.7 or maybe later.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
