Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: "Commons HttpClient Project"
 <commons-httpclient-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Subject: RE: HttpClient 3.0 is kind of done. Feedback needed
From: Oleg Kalnichevski <oleg.kalnichevski@bearingpoint.com>
To: Commons HttpClient Project <commons-httpclient-dev@jakarta.apache.org>
In-Reply-To: 
 <9FB7954D776ED511AF970004ACD36B820414E5C8@mn-msp-exch.oldrepublictitle.com>
References: 
	 <9FB7954D776ED511AF970004ACD36B820414E5C8@mn-msp-exch.oldrepublictitle.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1095342598.2474.164.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Thu, 16 Sep 2004 15:49:58 +0200


Tom,
I expect the new site to be on-line by the end of the week. Meanwhile
you can take a look at the list of enhancements and bug fixes here

http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/release_notes.txt?view=markup

New features:
-------------

(1) Architecture

 * New preference architecture

 * Improved exception handling framework

 * Granular non-standards configuration and tracking
 
 * Improved HTTP Version configuration and tracking
 
 * Support for streaming entities

 * Support for tunneled HTTP proxies via the ProxyClient

 * Ability to abort execution of HTTP methods

(2) Connection management

 * Support for closing idle connections

 * Support for JDK1.4 connect timeout through reflection

 * Support for connection manager shutdown
 
(3) Authentication

 * Improved authentication framework

 * Plug-in mechanism for authentication modules
 
 * Interactive authentication support
 
 * Alternate authentication support

(4) Cookie management

 * Cookie specification plug-in mechanism

 * 'Ignore cookies' cookie policy

 * Improved Netscape cookie support

(5) Redirects

 * Cross-site redirect support 

Oleg

On Thu, 2004-09-16 at 15:36, Gerdes, Tom wrote:
> What is the web site... And what are the improvements?   
> 
> -----Original Message-----
> From: Michael Becke [mailto:becke@u.washington.edu] 
> Sent: Thursday, September 16, 2004 7:27 AM
> To: Commons HttpClient Project
> Subject: Re: HttpClient 3.0 is kind of done. Feedback needed
> 
> I agree.  I think we're ready for another 3.0 release.
> 
> There has been surprisingly little comment on the 3.0 API, and I'm also
> concerned about freezing it until we've had more feedback.  We definitely
> have a "chicken and the egg" problem here.  My preference is to continue
> with a new 3.0 alpha release, and make a concerted effort to get it in front
> of people.
> 
> One area that we have been lacking is in promotion of 3.0 on the web site.
> Currently the only mention of it is on the status page.  Perhaps we should
> make the 3.0 docs and javadocs available on the site, and try to reference
> them where possible from 2.0.  My feeling is that once people are aware of
> some of the 3.0 improvements they are willing to try it out, but unless they
> are HttpClient regulars they may not know it exists.
> 
> Come now Oleg.  You haven't been the "Evil Comrade" for some time now :)
> 
> Mike
> 
> On Sep 16, 2004, at 5:52 AM, Oleg Kalnichevski wrote:
> 
> >
> > Folks,
> >
> > It looks like HttpClient 3.0 is not only ALPHA2 ready, it is almost 
> > code and feature complete. There are only 5 open tickets targeted for 
> > 3.0 FINAL. It may take me just a couple of days to get all the 
> > remaining issues dealt with, if needed.
> >
> > http://nagoya.apache.org/bugzilla/buglist.cgi? 
> > bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailty
> > p 
> > e1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailrep
> > o 
> > rter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfie
> > l 
> > dto=Now&chfieldvalue=&product=Commons&component=HttpClient&target_mile
> > s 
> > tone=3.0+Alpha+2&target_milestone=3.0+Beta+1&target_milestone=3.0+Beta
> > + 
> > 2&target_milestone=3.0+Final&short_desc=&short_desc_type=allwordssubst
> > r 
> > &long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_t
> > y pe=allwordssubstr&keywords=&keywords_type=anywords&field0-0
> > -0=noop&type0-0-0=noop&value0-0
> > -0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time
> >
> > Unless we start getting considerably more feedback, HttpClient 3.0 
> > development will stall completely.
> >
> > I sense there are lots of folks who are not willing to port their code 
> > from 2.0.x to 3.0 because the 3.0 branch is still considered unstable.
> > At the same time HttpClient 3.0 will stay there unless people start 
> > porting.
> >
> > I think it is really import to call an API freeze rather sooner than 
> > later. That will enable to drop newer releases in place of older ones 
> > and should give people enough confidence to start the transition from 
> > 2.0.x to 3.0. But before the API can be formally frozen I would really 
> > like to hear some feedback from our users and peer open-source 
> > developers. So far we have had virtually no feedback on the new API 
> > and I am concerned that we may see an avalanche of change requests as 
> > soon as we formally announce the API freeze and move closer to the first
> RC.
> >
> > How does everyone feel about it?
> >
> > Please share your ideas with me. I also have a few, but they all range 
> > from 'ugly' to 'very ugly' and may involve my wearing my 'Evil Comrade'
> > hat and threatening people with some nasty stuff ;-)
> >
> > Anyways, before things turn ugly, give us some feedback, 
> > pleeeeeeeeeeese
> >
> > Oleg
> >
> > **********************************************************************
> > *
> > ****************************
> > The information in this email is confidential and may be legally 
> > privileged.  Access to this email by anyone other than the intended 
> > addressee is unauthorized.  If you are not the intended recipient of 
> > this message, any review, disclosure, copying, distribution, 
> > retention, or any action taken or omitted to be taken in reliance on 
> > it is prohibited and may be unlawful.  If you are not the intended 
> > recipient, please reply to or forward a copy of this message to the 
> > sender and delete the message, any attachments, and any copies thereof 
> > from your system.
> > **********************************************************************
> > *
> > ****************************
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:  
> > commons-httpclient-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:  
> > commons-httpclient-dev-help@jakarta.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
commons-httpclient-dev-help@jakarta.apache.org
-- 
Oleg Kalnichevski | Senior Consultant | BearingPoint | Switzerland
Phone +41 43 299 6449 | Mobile +41 79 653 2562 | Fax +41 43 299 6550
www.bearingpoint.com

***************************************************************************************************
The information in this email is confidential and may be legally privileged.  Access to this email by anyone other than the intended addressee is unauthorized.  If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful.  If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
***************************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org