On Fri, 2006-05-05 at 22:19 +0200, Roland Weber wrote: > Hi Oleg, > > > The whole idea of HttpComponents was to reduce coupling between distinct > > sets of components within HttpClient in order to lower the entry barrier > > for new contributors by allowing them to concentrate on specific HTTP > > aspects without having to deal with intricacies of the entire HTTP > > stack. > > Oh, I thought the main idea was to have a pick-and-choose collection of > components for the users. >
Roland, All I am saying I do not think having a _separate_ release cycle for HttpCookie, HttpAuth, HttpConn provides us with any tangible benefits that outweigh extra managerial overhead at _this_ point of time. Those components will not be _versioned_ and _released_ separately from HttpClient. I absolutely does not mean they cannot be _packaged_ separately. > > By factoring out low level transport aspects into HttpCore we > > have already made a good progress toward this goal. Until we get more > > people on board I do not think splitting things further into HttpCookie, > > HttpAuth, HttpConn helps that much. > > I'm not saying that we should split now. In fact, I fully support > the approach of developing the remaining code in HttpClient for the > foreseeable future. What I want to have clarified is whether this > is a pragmatic decision on the implementation level, or whether this > is an indication for changes in our project goals. > It is neither. At this point of time it is just a matter of convenience and development speed. The critical juncture will be the first BETA release of HttpClient 4.0 Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
