Hi Oleg
I think I have a slightly less hacky work-around for the problem. How
about creating a custom version of ContentDecoderChannel that catches
ConnectionClosedException and re-throws it as a runtime exception of
some sort? This would enable your code to handle truncated messages and
would not require the hack to be applied to HttpCore? Would that work
for you?
If this is possible, it will be fine. However it seems like this is hard
coded in NHttpConnectionBase.createContentDecoder() .. is there an easy
way I did not notice to register my own decoder?
I also believe we should release HttpCore 4.1.1 without a fix for the
problem and take more time to work out a proper solution in the 4.2
branch. Would that be acceptable?
Yes.. this is not a blocker for me, and does not need to hold the
release further
thanks
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
