> Hey, we're simply users, not developers of HttpClient! :-) > Vincent, what is wrong with trying to influence the course of HttpClient development when development plans are being publicly discussed, but not after a decision has been taken? There is nothing that precludes you from voicing your opinion on issues that are important for you.
> > > > Please also advice me how to fix these bugs while retaining 2.0 API > > compatibility: > > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20089 > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16729 > > I fear I am not able to help much as I'm not an HttpClient developer and > I would need to dive in the code to give any help. That said, there are > always ways to evolve an API by going through a deprecation mechanism. > It is not a problem to mark a method as deprecated. The problem is to keep deprecated stuff fully functional once the overall architecture has undergone some significant changes. I do not see at as always feasible. In my humble opinion 2.0 API has been REALLY stretched to its very limit and have done everything possible within the constraints of the existing architecture. Guys, please try to see a bit beyond your own project and your own interests. Cheers Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
