Mladen Turk wrote:
Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
+ Integer i =
responseTransHash.get(header.toLowerCase(Locale.US));
-0. The String operations take away any benefit this could have.
Perhaps for CPU usage on the Tomcat, that is annihilated by the
lower processing on the mod_jk side.
It seems the CPU is more important on the application server side.
Obviously, one garbage string is not very important, but I did bother
optimizing the rest, so I appreciate when others try to do the same
thing too.
Also the network traffic is much
lower.
I don't see how there can be a bandwidth issue between the front end
server and the appserver.
The standard header having Content-Type, Content-Length and Date
is 30 bytes smaller.
Silly me who thought the actually relevant bandwidth was between the
front end and the client ;)
If we can guarantee header names will always be in the proper
case, the toLowerCase can be omitted, or by using something
other to compare with array of string.
It's up to you if you want to add this feature. At the moment, I think I
have to be against this change because the implementation is simply ugly.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
