Thank you Oleg. We¹ll stick with it then since it won¹t do any unexpected
harm. The destination HTTP/s server may actually hold the request for 10+
seconds which is ultimately more costly than simply rebuilding a fresh
connection.
‹
Pete
On 3/29/16, 6:42 AM, "Oleg Kalnichevski"
On Fri, 2016-03-25 at 18:42 +, Pete Keyes wrote:
> Are there any significant downsides to using HttpRequest.abort() to signal
> that a request should give up as soon as possible? Knowing that this is a
> blocking I/O not the apache async client. Or, is simply better to let it go
> on
Are there any significant downsides to using HttpRequest.abort() to signal that
a request should give up as soon as possible? Knowing that this is a blocking
I/O not the apache async client. Or, is simply better to let it go on
naturally and discard the request’s response whenever it
