On Sun, 2006-02-26 at 22:28 -0500, Michael Becke wrote:
> I have checked in a first try at reworking the goals and scope page. 
> Please let me know what you think and feel free to make any changes.
> 
> Mike
> 

Hi Mike,

This is certainly a more positive way of looking at things and a more
appropriate way to describe goals of the project. However, without some
contextual information (which we all know but others may not) the
rationale behind certain motives may not be entirely clear. Can we keep
the description of HttpClient 3.0 design limitations in some form? The
goals page could contain some references to this page providing
necessary context for the design decisions driving HttpComponents
development?

Oleg 


> On 2/26/06, Michael Becke <[EMAIL PROTECTED]> wrote:
> > On 2/26/06, Roland Weber <[EMAIL PROTECTED]> wrote:
> >
> > > I also think we should have dummies for the other planned modules, in
> > > particular HttpCookie and HttpAuth. It will help people to understand
> > > which features are *not* to be expected in HttpCore.
> >
> > Yes, good idea.  Might as well lay it all out and fill in when things are 
> > ready.
> >
> > > Regarding goals and scopes, I divert from Mike's suggestion. Instead
> > > of having a section that talks about HttpClient deficiencies and then
> > > adds details on how we want to address them, I would prefer to
> > > state goals and then add details about the HttpClient deficiencies
> > > from which these goals are derived. Simply reversing the headlines
> > > of the current page would already help:
> > >
> > > [Componentized Design]
> > > [Cleanly structured API]
> > > [Minimal external dependencies]
> >
> > Yep, I like this better.  I'll take a crack at it this afternoon if no
> > one beats me to it.
> >
> > Mike
> >
> 
> ---------------------------------------------------------------------
> 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