Hi Henri, thanks for the explanation.
> Moving to Web Services seems odd to me, though I guess they're the > last remaining umbrella out there (XML is at the 'there's no one left > to turn the light out' stage) so that would be an advantage. > Personally I don't see why not on the TLP bit. Because Oleg is basically doing all the work on his own. There are enough PMC around to pass votes, but that's it. If HttpComponents goes TLP and Oleg has to write board reports in addition to all the coding, the project will suffer. As it will suffer from writing a proposal to move, but I guess that can't be helped. Web Services, or rather Synapse, are the first Apache users of the 4.0 codebase (I am aware of). They are very active, and have an interest in keeping at least the HttpCore part going. We don't have any newcomers aspiring to become committers at the moment. We hope that will change with the new codebase, but there is no telling how long it will take. Hanging around with an active user base is our best chance to keep the project going long enough. > Why not just move Commons HttpClient into HttpComponents? I expect that to happen. > And then to wherever? The 3.x codebase has a bad design. We'd like it to go away and fade into oblivion when the 4.0 codebase has reached the point to replace it. That's why I suggested to leave it behind in a dying Jakarta :-) Of course I was merely being sarcastic. We know it won't go away for years, and HttpComponents will have to support the old codebase for a long time to come. Somebody would veto that kind of trick anyway. > It stopped being a part of Commons when the mailing lists > were split (again hindsight). That was before I got here. And it is the reason why moving back to Commons is not the first choice. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
