Oleg, thanks for the quick and extensive answer!
> This is a conscious design decision. The reason for these wrappers' > existence is to ensure the reliability of persistent connections. I already assumed something like that. Bummer. > We are perfectly aware of shortcomings of the existing HttpClient API. > It is butt ugly, plain and simple. I guess I am entitled to such a > strong opinion as I have been maintaining HttpClient for years on a day > to day basis. Well ...that sounds worse than it feels from the users POV :) Although I have this problem currently. > HttpClient is currently being rewritten and its API redesigned from > scratch to address those shortcomings and provide a flexible platform > one could use to build client-, proxy- and server-side HTTP services. I > hope we will have a much cleaner and powerful API as a result: > > http://wiki.apache.org/jakarta-httpclient/HttpClientApiRedesign Thanks for the pointer looking forward seeing it in action. > There's already enough code in the SVN to check out already and get a > feel of how things are shaping up > > http://svn.apache.org/repos/asf/jakarta/httpclient/trunk/http-common/ Currently too much on the plate but hope to have the time to try it anytime soon. cheers -- Torsten
signature.asc
Description: OpenPGP digital signature
