On Sun, 2012-07-08 at 23:25 +0400, Dmitry Potapov wrote: > Oh, this sounds surprising for me, I was sure that callback will be > functional until request processing completion. > Using this bundle of knowledge, I've put > HttpAsyncExchange.submitResponse() after heavy-weight task execution, > and got required behaviour — Cancellable.cancel() was called ≈1ms > after connection termination. > > BasicAsyncResponseProcuder.close() overriding also makes sense for me, > as it a much more handy that IOException. > > Frankly speaking I haven't noticed any differences in HttpCore > behaviour between 4.2.1 and r1358777: both works fine with > HttpAsyncExchange.submitResponse() called right before response > generation and BasicAsyncResponseProcuder.close() overloaded to call > Cancellable.cancel() >
Cool. Let me know if you need further help. Олег --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
