I've been out for a while, so it might be a stupid question. Do you serve
the script via a servlet or is the file served directly?
I ask because last year I did some performance tests for a client and having
a servlet write a string is very expensive, compared to serving a static
file. 100ms
Yes +1 for that, I will work on the issue later this year again, my
guess is we probably can enable it via a chain and event listener system
and header manipulation, but I have more important work pending, but I
want a solution which enables debugging for all users for 2.0.1. So if
we go that
Am 26.06.10 11:39, schrieb Jan-Kees van Andel:
I've been out for a while, so it might be a stupid question. Do you
serve the script via a servlet or is the file served directly?
The files are resources within the api package so they are basically
served from the standard faces-servlet.
I
Hello
I have been doing some performance tuning for the last day on our jsf.js
scripts. So far things look good, the performance seems to be slightly
faster (about 5-15% on a modern browser) than Mojarras under my testing
conditions, except for one area.
jsf-uncompressed.js does not work out
Hi Werner
I think we should activate it with a web config param. Debug using the real
scripts in firefox is really useful. The idea could be provide a
jsf-uncompressed.js file with all scripts as default on dev mode, but have a
config param like
