It may be too a strong opinion, but I am convinced 2.0 API is not worth a single hour of further development beyond bug fixes. I will also strongly object any cross-site redirect fix at the expense of overall quality. I think we have spent enough time already coming up with all sorts of creative ways of bending 2.0 API and it simply did not work. There's no way I take part in anything similar to HttpMethodBase#fakeResponse method.
I agree. My desire is to leave 2.0 in the dust.
If it is just about release numbers, let us call it HttpClient 3.0, or HttpClient 3.1, or HttpClient NT, or HttpClient.NET, or HttpClient Whatever, but I finally want to be able to do things right
I guess you are right. It is mostly a case of semantics. What exactly do we mean by 2.1? The official description of a minor release does not really fit with our plans (which I still agree with). I do not think a 3.0 release is quite appropriate either though. Is there a middle ground? 2.55 perhaps:)
Sorry to bring all of this up again. Perhaps I should just stop worrying about it.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
