Hi Oleg
I think HttpAsyncClient 4.0-beta3 is quite stable as far as I can tell
by feedback from users. There has been only one serious bug reported
(HTTPASYNC-34, fixed in trunk). A few months back CXF project chose it
over all other HTTP clients as their default async client side HTTP
transport after extensive evaluation. They seem to be OK.
Thats great to hear!
Having said that I have been doing a lot of refactoring on it in my
local repository to improve performance and am also planning to migrate
it to HttpCore 4.3 API. There will be a period of instability ahead and
I do not expect it to go GA soon. If you do no not need a full blown
HTTP client with proxy, auth and cookie support stick to HttpCore for a
few more months.
Ok.. we will stick to HttpCore right now, as we do not need extensive
proxy or cookie support. However authentication support is something we
would like to utilize, especially the new NTLM support, SPNEGO and
Kerberos. I will ping the list if I need assistance incorporating those in.
thanks and regards
asankha
On 02/09/2013 10:47 PM, Oleg Kalnichevski wrote:
On Sat, 2013-02-09 at 11:26 +0530, Asankha C. Perera wrote:
Hi All
We are in the process of migrating our code to the latest versions of
HttpCore / NIO and I was wondering how stable the Async Client is right
now for possible production use. Should we expect many more releases /
major API changes until it becomes GA, or are we close to a GA being in
the 3rd beta?
regards
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]
