Agreed. Sounds like the right approach. Mike
On 12/8/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
Folks, With HttpCore ALPHA3 finally out the door, I think it is time we put HttpCore on the back burner for a while and took a first stab at HttpClient 4.0. Here is my Evil (tm) Plan. There are many things I never liked about HttpClient 3.x API. High on my list are HttpConfiguration, HttpState, HttpConnection, HttpCookie. While I am convinced there are better / cleaner ways to go about HTTP state management, host configuration and connection management, these classes are not broken beyond redemption the same way HttpMethod and HttpMethodBase are. In my opinion HttpCore fixed those things that were broken really badly about HttpClient 3.x. So, as a first step I suggest that we simply try to port HttpClient 3.x code to HttpCore without any drastic changes in client side protocol code and see how that comes about. Once we have something working and delivering equivalent functionality to that of HttpClient 3.x, we could take a step back, take a hard look at those things that are still sub-optimal and decide which of those need to be redesigned. How does that sound? Evil Comrade Oleg --------------------------------------------------------------------- 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]
