I agree with this to certain degree. The presence and HttpClient and HttpMultiClient is extremely confusing to the user. Although HttpMultiClient is what most people really need, most people will take the wrong guess and use HttpClient. Maybe we should just rename HttpMultiClient to HttpClient. Another issue is the design is pretty much hard-coded, it's not easily extensible without hacking the source code. Two examples are authentication and cookie policy. It's very difficult and inefficient to add new authentication method and change cookie policy without changing the source code. In addition, I would suggest to think about the real value of having an http client v.s. java.net.*. An obscure "quickly running into the limitation of java.net package" is not good enough. User need a way to quickly find out if they need to use httpclient or not. More discussion should happen on the overall design and more attension should be paid to real user's needs for httpclient. just my oppinion.
xiaowei -----Original Message----- From: Amir D. Kolsky [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 9:52 AM To: Jakarta Commons Developers List Subject: RE: HttpClient development As a developer new to HttpClient I have to admit to be extremely confused by the package. Several usage models are concurrently impelemented, virtually no documentation exists as to how to do what, and worse, it appears that there is no one at the helm to guide this package in a coherent and architectured manner. If HttpClient is to succeed, then beyond being bug free (as much as possible), and adhering to the RFCs, it must present a coherent and well documented interface to the programmers who are to use it. If you guys are willing to invest some time in designing the HttpClient NG (as some organizations like to call their next release), I would be happy to actively participate in it. There must be, however, someone coordinating this effort -- making sure that design, implementation, documentation and the test suite are all complete and in sync... Otherwise, frankly, I don't see a real chance of this package taking off and being used by anyone beyond those actually developing it, and it will lose big time to HTTPClient. Amir -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
