https://bz.apache.org/bugzilla/show_bug.cgi?id=57808

--- Comment #4 from Philippe Marschall <kus...@gmx.net> ---
I have read bug 51400 and my understanding is that preloading is not necessary
to avoid performance bottlenecks. Preloading was discussed but I couldn't find
the reasons why preloading was ultimately chosen. The reasons for other
implementation decisions I could find (not caching misses, not storing
permutations, …).
My understanding is that avoiding calling (indirectly) Charset.forName() /
Charset.lookup() during normal request processing is necessary to avoid
performance bottlenecks. This is achieved by the caching even when avoiding the
preloading.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to