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. > 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. > Maintaining those components as separate modules will just > put extra burden on the actual committers Will this be an extra burden for maintaining, or are we talking about the one-time effort of creating the additional components? I am fine with delaying the one-time effort until somebody volunteers. But I do not see an additional ongoing overhead. Please point it out to me if I am missing something. > and will result in more JARs > the users will have to download and deal with. To put it with your words: there are other ways to deal with multiple JARs ;-) That is surely a problem we have to address before splitting into more components. No argument there. > We should not do it > unless it is clearly driven either by demand from the users or by > contributions from new project participants willing to help maintain > those components. > > Let us be pragmatic. Those new contributors may never materialize. A more realistic scenario is that sometime next year or the year after, I am much more familiar with JIRA and our release and deployment processes. It doesn't happen often, but sometimes I do feel like performing some non-coding administrative tasks I would usually run away from. So if I should be in that mood, at a very distant time in the future: could I simply volunteer to create the additional component we always wanted to have, or would I have to start a new discussion why some of the code should be moved into a separate component in the first place? Because if there needs to be a discussion, I prefer to have it now while I am the one sticking to the old plan, while you have to come up with the arguments for changing it. Again: I am _not_ suggesting to create the other components now, nor anytime soon. Neither am I going to ask you to create them in the future. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
