> It looks like it is going to be a very dull and uneventful weekend here > and I'll have some spare time to work on the new HTTP components for > HttpClient 4.0. I'll be mostly writing boring test cases since the test > coverage slipped from 80% to 50% as a result of code refactoring > intended to improve performance. The test coverage needs to be > improved.
Might be the same here. I plan to do some work on HttpClient this afternoon and tomorrow. > At the same time I would like to suggest some design level changes > > * I would like to move all NIO related code from HttpCommon to > HttpAsync. Hence on NIO will be used for non-blocking HTTP only. > Blocking NIO proved inferior in terms of performance to classic IO, and, > frankly, is useless for blocking HTTP. Yep > * Rename HttpCommon to HttpBase (better name suggestions are welcome) to > avoid confusion with Jakarta Commons HttpBase works. Also perhaps HttpCore/CoreHttp. > * Rename HttpAsync to HttpNIO. In my opinion NIO (as in non-blocking > I/O) should be more descriptive and recognizable to an average Java folk > than async. Sounds good. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
