Mike, I can guarantee that there will be no API changes of what so ever as long as you are using stable 2.0 branch. However, if we are no allowed to change even internal APIs on the development 2.1 branch, I personally might also just seriously consider stopping contributing to HttpClient at all.
Oleg Is that the general development strategy? I ask since I am about to try to integrate the HttpClient 2.0 beta 2 into an existing framework. I would be doing this to benefit from robust and performant communication with servers, not from features provided by the HttpClient class. For exaple, regardless of whether the HttpClient class handles redirects properly now, I will never use it to transparently handle them as I need to see them and handle them myself. If I am to be forever doomed to continual revisions due to 'internal' api changes because I don't go through the HttpClient class then I may have to reconsider whether I can use the library. After reading through "http://jakarta.apache.org/commons/httpclient/tutorial.html"; I see that there is no distinction made between "HttpClient" the library and "HttpClient" the class. Is this deliberate? Sorry for beating on you people for this, and I realise I am probably in a minority, but there is not much point in me going down this route if I am destined to have to drop it all. Ta, -- Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
