-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
On 2/20/2009 11:25 AM, Christopher Schultz wrote:
> Unfortunately, I wasn't able to get a complete response captured because
> of the timing of various events during the request (in summary: the
> HttpProcessor does some stuff at the last minute that we can't capture
> using application code).
A shower and shave have given me some time to reflect on this.
The original requirements were to record request/response data in order
to /simulate the application/, not to create a complete log of
everything that happens.
In my efforts to record everything, I forgot that the goal wasn't to
record a complete HTTP conversation (as the name of my filter's class
would indicate). I came to the realization that the response will be
replayed /inside the server/ that I've been having difficulty in
instrumenting. That means that the inability to (gracefully) intercept
server-originating headers, etc. is not a problem: I'm only simulating
the application's response to a particular request, not the server's
response.
So, I'm resuming my efforts to complete the response side of the
equation. I'll post more code when it's available.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkme7S0ACgkQ9CaO5/Lv0PDQTQCeMfKYz+pP3UXhA+Acx1YOUk/s
7GgAnj+KeVvGW2MZ+q0gFBFnXwVjNCy4
=Qror
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
|