On Wed, 2005-08-31 at 13:28 -0700, Eric Johnson wrote: > A good start indeed. > > It seems to me that explicitly identifying the RFCs and specs that will > be addressed would go a long way towards clarifying what it *DOES* and > *DOES NOT* do. >
Good idea, Eric. Actually after having looked at the HttpClient features page [1] I just realized that even existing project scope does not inhibit development of server side components. The first line clearly states "Standards based, pure Java, implementation of HTTP versions 1.0 and 1.1". There's no mentioning of client-side only scope. Oleg [1] http://jakarta.apache.org/commons/httpclient/features.html > -Eric. > > Oleg Kalnichevski wrote: > > >On Sun, 2005-08-28 at 17:25 -0400, Michael Becke wrote: > > > > > >>Now that we've gotten the ball rolling, let's try to focus a little > >>more on HttpClient's charter as we move to Jakarta level. This is the > >>document that will define our goals, name, and what exactly is or > >>isn't in bounds as far as development goes. > >> > >> > > > >Folks, > > > >I have taken liberty of throwing together a first draft of the new > >project charter based on the ideas expressed so far > > > >http://wiki.apache.org/jakarta-httpclient/NewProjectCharter > > > >Please do not be shy and add your ideas, comments, and raise objections > >if you think something is wrong > > > >Oleg > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
