On Monday, Jul 21, 2003, at 09:32 Europe/London, Kalnichevski, Oleg wrote:
Mike, I can guarantee that there will be no API changes of what so ever as long as you are using stable 2.0 branch. However, if we are no allowed to change even internal APIs on the development 2.1 branch, I personally might also just seriously consider stopping contributing to HttpClient at all.
I understand this as a recent bugbear of yours :-) I am not asking for no change, far from it. Instead, what I am asking is: what is the supported 'user profile'? For example, will this profile support 'component assemblers' as well as 'User-Agent users'? From my point of view I see the HttpClient library as a grab-bag of components to stick together, not a single entry point.
I have followed the discussion around the need to refactor the internals of the HttpClient library for some time and I would certainly agree that they need reworking. But what is the end goal? Is it "almost a User-Agent (just add water)" ie the HttpClient class-to-be?
The main reason I am coming to the HttpClient library is because existing solutions such as the Sun one or innovation.ch have bugs or aren't transparent enough. I already have a User-Agent which does everything the HttpClient class does. I just need a way to plug in an HTTP 1.1 provider which performs better and does not have the same bugs/deficiencies as Sun/innovation.ch. If you wish I can itemize exactly what is wrong with these libraries and tell you what I need.
Again, many thanks for the work (I think I've probably spent more time and chars talking about this issue than I'll use doing the actual work :-) )
-- Mike Moran
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
