On 5/1/2014 7:30 PM, Christopher Gross wrote: > The message implies that there is a better way of having XSLT > transformations. Is that the case, or is there just this perpetual warning > for normal operations?
When I was using XSLT, I got a warning for every core, even though I had a cached lifetime that would prevent problems. I don't remember what that lifetime was any more, probably at least five minutes, but it might have been longer. I also met the other criteria -- there was only one XSLT defined. Perhaps the warning needs to be suppressed if the lifetime is above a certain value and there is only one transform defined? I would expect that even 60 seconds would be a long enough lifetime to prevent major issues in high load scenarios ... but we could bikeshed that number forever. Thanks, Shawn
