On Tue, 2013-05-07 at 17:25 +0200, Walco van Loon wrote: > Hi Oleg, > > We have an implementation of tracing to files in place, based on the 4.1 > API. > > In 4.2.3, there was an issue that a custom ClientConnectionOperator was not > honored everywhere, but that is now fixed. The issue that remains is that > we had a suboptimal approach to close the forked streams if a response is > complete in case of persistent HTTP connections, an event that is not > "signaled" in our custom OperatedClientConnection. > > This approach consists of an override of the method > PoolingClientConnectionManager.releaseConnection(), and using reflection to > get our custom connection implementation from the ManagedClientConnection > in order to close the forked file input/output streams we allocated earlier. > > Regards, > Walco >
Walco If I understand it correctly and your goal is to enhance connection instances with additional functionality on a per request basis I am afraid the only proper solution would be to develop a custom connection manager. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
