On 8/26/05, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > On Fri, 2005-08-26 at 11:34 -0700, Gordon Mohr wrote: > > I may have missed something -- but the answer doesn't seem to be in this > > thread. > > > > What's wrong with 'HttpClient'? > > > > FWIW, this project under its current name 'owns' the term 'HttpClient' > > via the major search engines; that's usually how I get to the > > project pages for news, source dumps, etc. > > > > If the aim is to make a broader name to also encompass additional > > related work, I would suggest some sort of extension to 'HttpClient' > > preserving it as a name token, like 'HttpClient Toolkit' or some such. > > > Gordon, > > This is an unfortunate side effect of internal Jakarta politics. There's > nothing wrong with the name. To a certain extent it is a brand. The > trouble is that we might be not permitted to release server side HTTP > components because some believe that may constitute a breach of the > project charter (whatever that mean since we do not have a charter > yet).
A bit stronger than the current situation I think. There was a comment on server-stuff being outside the Commons HttpClient charter, but as Oleg pointed out, the Jakarta HttpXxxx charter is currently undefined. My opinion, which is pretty worthless though I do have a robots.txt parser I'd like to contribute when you get setup for said components, is that the name should be: HttpComponents and that you split said components into: * Http Client Components (maintaining name) * Http Server Components on the navigation system. Naming yourself HttpComponents should help with two of the larger confusions (ie - you won't be releasing a full HTTP server implementation and you're not seeking to create an alternative to the Servlet API). Not that either of those were considered outright bad, just that we ought to talk with the ASF as a whole before doing them. Biggest problem with the above might be complaints from the Apache HTTP Server project about the 'Http Server Components' subtitle, which can either be solved by putting Java(tm) on the front or having a big debate about rearranging the ASF :) - Two further questions: 1) Will you be releasing these components as separate jars? ie) is HttpC**** about to become an umbrella subproject like Taglibs/Commons/Turbine/Silk? 2) How does this balance with the Silk - Web Components subproject? Where shall we draw the line between HTTP and Web? Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
