On Mon, 2002-05-06 at 12:52, Amir D. Kolsky wrote: > 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.
i must agree with this point. as a new developer, without any sample code or usage instructions to work from, i simply latched onto the HttpClient object, even though HttpMultiClient is probably more generally useful. a little bit of documentation would go a long way towards making this package more popular. > 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. speaking of coherent, i have two minor nitpicks in that regard: 1. the java world seems to have been making a concerted effort to consistently use FooURLName instead of FooUrlName in java identifiers. suggest the UrlFooMethods be altered to conform. 2. i wish the UrlFooMethods operated on URL objects instead of String URLs. > 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. that, frankly, does bother me. i chose to use HttpClient since i prefer to avoid *GPL libraries when developing applications for work, but many developers base their decisions more on features, docs, and project activity. - donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
