On Thu, Oct 06, 2005 at 10:51:24AM +0100, robert burrell donkin wrote:
> just a few more from me:
> 
> * Jakarta Http Components  continues the development of  Jakarta
> HttpClient  (formerly  Jakarta Commons HttpClient ) based on the toolset
> of HTTP components. This tool focuses strictly on the client side of
> HTTP.
> 
> ->
> 
> * Jakarta Http Components  continues the development of  Jakarta
> HttpClient  (formerly  Jakarta Commons HttpClient ) based on the toolset
> of HTTP components. This tool focuses on the client side of HTTP.
> 
> 'strictly' is an unnecessary and subjective qualifier so probably best
> removed.
> 
> * Jakarta Http Components  MAY develop non-client components (such as an
> HTTP connector, a lightweight server component, proxy components) as
> reference material to demonstrate the capabilities of the toolset. The
> said artifacts ARE NOT meant for production use and are not released as
> official Apache Jakarta products.
> 
> ->
> 
> * Jakarta Http Components  MAY develop application layer components
> (such as an HTTP connector, a lightweight server component, proxy
> components) as reference material to demonstrate the capabilities of the
> toolset. The said artifacts ARE NOT meant for production use and are not
> released as official Apache Jakarta products.
> 
> this fits in better with the rest of the draft: low level transport
> layer APIs suitable for use on servers may be developed but application
> layer components (whether client or server) may only be developed as
> demonstrations. 
> 
> i'd also like to add a new clause:
> 
> * Jakarta Http Components is additional charged with the maintenance of
> the existing jakarta-commons httpclient component. 
> 
> this makes it clear that the sub-project can and will maintain the
> existing httpclient components even if they would not longer be
> considered in-scope.
> 
> all just IMHO, of course
> 

Hi Robert,

I believe the changes you have suggested are quite reasonable. Please do
not be shy and feel free to tweak the draft of the project charter directly
in the Wiki:

http://wiki.apache.org/jakarta-httpclient/NewProjectCharter

Cheers,

Oleg


> - robert
> 
> On Thu, 2005-10-06 at 01:10 -0400, Henri Yandell wrote:
> > Any more comments before I call a vote?
> > 
> > Hen
> > 
> > On Sat, 24 Sep 2005, Henri Yandell wrote:
> > 
> > >
> > > Prior to calling a PMC vote here in a week or two, I'd like to ask if 
> > > anybody 
> > > has any comments on the following proposal for Commons HttpClient to 
> > > become a 
> > > Jakarta subproject focusing on Http components.
> > >
> > > Hen
> > >
> > > *********************************************************************
> > >
> > > (The following charter for Jakarta Http Components project is pending 
> > > approval of the Jakarta Project Management Committee (PMC). )
> > >
> > > Rationale:
> > > =========
> > >
> > > The original Jakarta Commons HttpClient API has a number limitations that 
> > > cannot be resolved without a significant architectural redesign. 
> > > Moreover, 
> > > Jakarta Commons HttpClient has been increasingly used in applications and 
> > > environments it has not been specifically designed for. The existing 
> > > monolithic design no longer adequately reflects the use patterns of 
> > > HttpClient.
> > >
> > > HttpClient needs to be refactored into a toolset of simple, low level 
> > > HTTP 
> > > components suitable for building more specialized HTTP services.
> > >
> > > Project scope:
> > > =============
> > >
> > > * Jakarta Http Components develops a toolset of low level components
> > > focused exclusively at the transport aspects of HTTP protocol.
> > >
> > > * Jakarta Http Components MUST be content agnostic. The project DOES NOT
> > > develop components intended to produce or consume content of HTTP
> > > messages.
> > >
> > > * Jakarta Http Components continues the development of Jakarta
> > > HttpClient (formerly Jakarta Commons HttpClient) based on the toolset of
> > > HTTP components. This tool focuses strictly on the client side of HTTP.
> > >
> > > * Jakarta Http Components MAY develop non-client components (such as an
> > > HTTP connector, a lightweight server component, proxy components) as
> > > reference material to demonstrate the capabilities of the toolset. The
> > > said artifacts ARE NOT meant for production use and are not released as
> > > official Apache Jakarta products.
> > >
> > > * Jakarta Http Components collaborates with other projects to develop 
> > > specialized HTTP services for production use based on the toolset of HTTP 
> > > components.
> > >
> > > * Jakarta Http Components DOES NOT define a server side API on top of the 
> > > low 
> > > level transport API.
> > >
> > > Targeted specifications and standards:
> > > =====================================
> > > * RFC1945  Hypertext Transfer Protocol -- HTTP/1.0
> > > * RFC2616  Hypertext Transfer Protocol -- HTTP/1.1
> > > * RFC2617  HTTP Authentication: Basic and Digest Access Authentication
> > > * RFC2109  HTTP State Management Mechanism -- Cookies
> > > * RFC2965  HTTP State Management Mechanism -- Cookie2
> > > * A standard for robot exclusion - robots.txt parser (contribution 
> > > requiring 
> > > Software Grant - http://www.osjava.org/norbert/)
> > >
> > > Initial set of committers:
> > > ==========================
> > > Project Lead
> > >  Michael Becke
> > >
> > > Project Committers
> > >  Adrian Sutton
> > >  Ortwin Glueck
> > >  Oleg Kalnichevski
> > >  Henri Yandell
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to