-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Antonios,
On 2/24/2011 11:28 AM, Antonios Kogias wrote: > And I would like some clarification on "Depending on exactly where the > Valve falls within the Valve chain and how the RequestDispatcher works > with Valves, it may or may not include time to render the response at all." If your servlet redirects to a dynamic response, then the time for the first request necessarily does not include the time to render a response (unless you consider issuing a 30x status to be "rendering the response"). That seems clear to me. On the other hand, your servlet can issue a "forward" which is essentially a server-side redirect that allows a second (or third, or fourth, ...) servlet to generate a response after the first servlet does it's work. I'm not sure where the Valve chain fits into that (does the AccessLogValve time the calls to each individual forward, or does it time the entire request/response as the client sees it?), but the answer to that question can significantly change the timings that you observe. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1rxdEACgkQ9CaO5/Lv0PCmDQCeLofJSFjkIDeFElfWU9Q10sc2 sQUAni1wjqcATxwpi8+Y5Z8i8yr5qN71 =7144 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
