Torsten Curdt wrote:
...or am I really mistaken?
JNI calls are always expensive, and in some scenarios (IIRC, on Mac OS X it is
*very* expensive to do File.getCanonicalName) it can be even worse.
And if you take site of middle complexity, and take into account all sitemap
aggregations, XSLT includes, and so on, you can end up with dozens of JNI file
system accesses for *each* request.
Here, either delayed validity or complete turn off of checking helps a lot.
I'm in favor of having both configurable delay for checks, and having an option
to turn off checks, per category:
* sitemaps
* xslt files
* xml files, etc
Vadim
