I created a little httpclient aborting client application so that we can test how our server handles the equivalent of the user shutting down their browser in the middle of an operation or unexpectedly hitting back etc.
Basically a server post (though it wouldn't need to be) is kicked off and then in another thread a timer kicks in and aborts the application. Has anyone else done something similar? Would using HttpMethod#abort be the preferred way to do this rather than the current brute force approach I have taken? I presume it can be fired off in a separate thread to the original executeMethod()? Is there some way to ensure that the connection is definitely canceled? If my timeout value is too large, sometimes the operation has already finished. If my timeout value is too small, sometimes the connection hasn't been established yet. I would prefer to adopt an approach that was less brittle. Thanks for any advice, Paul. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
