You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Oleg Kalnichevski <ol...@bearingpoint.com> on 2004/09/16 11:52:01 UTC
HttpClient 3.0 is kind of done. Feedback needed
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=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Commons&component=HttpClient&target_milestone=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=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=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
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Ortwin Glück <or...@nose.ch>.
Oliver Köll wrote:
> I only have a minor feature request for the preferences architecture: it
> would be nice to be able to define default HttpMethodParams per
> HttpClient instance. (i'm not sure, but you may already have taken care
> of that).
Actually that was one of the design goals of the new preferences
architecture: To be able to set and override any parameter at any level.
--
_________________________________________________________________
NOSE applied intelligence ag
ortwin glück [www] http://www.nose.ch
software engineer
hardturmstrasse 171 [pgp id] 0x81CF3416
8005 zürich [office] +41-1-277 57 35
switzerland [fax] +41-1-277 57 12
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Oleg Kalnichevski <ol...@bearingpoint.com>.
No worries. The preferences API can be tricky. As soon as 3.0a2 is
officially out, there will be a new guide dealing exclusively with the
preferences API. Meanwhile you can get it from the CVS (as always)
Oleg
On Thu, 2004-09-16 at 18:16, Oliver Köll wrote:
> Hi Oleg,
>
> thanks for the tips - i'll check them out.
>
> They look rather obvious, too - i wonder why i didn't think of it :-(
>
> I think the preferences stuff is a little hard to figure out. I usually
> end up scanning through the sources being quite confused. OTH, when i DO
> grasp something, it looks rather smart to me.
>
> Regards, Oliver
>
>
> Oleg Kalnichevski wrote:
> >
> >>I only have a minor feature request for the preferences architecture: it
> >
> >>would be nice to be able to define default HttpMethodParams per
> >>HttpClient instance. (i'm not sure, but you may already have taken care
> >>of that).
> >>
> >
> > I believe that can be fairly easy accomplished using existing API
> >
> > option 1)
> > ========================================================
> > HttpClientParams params = new HttpClientParams(null);
> > params.setParameter("whatever", new Integer(1));
> > HttpClient client = new HttpClient(params);
> > ========================================================
> >
> >
> > option 2)
> > ========================================================
> >
> > DefaultHttpParams.setHttpParamsFactory(new HttpParamsFactory()
> > {
> > public HttpParams getDefaultParams() {
> > HttpClientParams params = new HttpClientParams(null);
> > params.setParameter("whatever", new Integer(1));
> > return params;
> > }
> > });
> > HttpClient client = new HttpClient();
> > ========================================================
> >
> > Options 1 and 2 produce similar results. See which one suits your
> > application better.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
***************************************************************************************************
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
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Oliver Köll <ok...@newbase.de>.
Hi Oleg,
thanks for the tips - i'll check them out.
They look rather obvious, too - i wonder why i didn't think of it :-(
I think the preferences stuff is a little hard to figure out. I usually
end up scanning through the sources being quite confused. OTH, when i DO
grasp something, it looks rather smart to me.
Regards, Oliver
Oleg Kalnichevski wrote:
>
>>I only have a minor feature request for the preferences architecture: it
>
>>would be nice to be able to define default HttpMethodParams per
>>HttpClient instance. (i'm not sure, but you may already have taken care
>>of that).
>>
>
> I believe that can be fairly easy accomplished using existing API
>
> option 1)
> ========================================================
> HttpClientParams params = new HttpClientParams(null);
> params.setParameter("whatever", new Integer(1));
> HttpClient client = new HttpClient(params);
> ========================================================
>
>
> option 2)
> ========================================================
>
> DefaultHttpParams.setHttpParamsFactory(new HttpParamsFactory()
> {
> public HttpParams getDefaultParams() {
> HttpClientParams params = new HttpClientParams(null);
> params.setParameter("whatever", new Integer(1));
> return params;
> }
> });
> HttpClient client = new HttpClient();
> ========================================================
>
> Options 1 and 2 produce similar results. See which one suits your
> application better.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Oleg Kalnichevski <ol...@bearingpoint.com>.
On Thu, 2004-09-16 at 16:00, Oliver Köll wrote:
> Oleg Kalnichevski wrote:
> >
> > Anyways, before things turn ugly, give us some feedback, pleeeeeeeeeeese
>
> Hi Oleg,
>
> i'm sorry, that i haven't given any feedback earlier, but i always felt,
> that my understanding of HttpClient wasn't deep enough to qualify any
> criticism.
>
> The good news: i'm already using HttpClient 3.0a1 in production for some
> time (i preferred it over 2.1 because of the improved Cookie handling),
> and i haven't had any problems with it yet. Actually, i'm feeling that
> the "alpha" categorization isn't doing the software justice :-)
>
Hi Oliver,
I am glad you found HttpClient 3.0a1 useful. Actually HttpClient 3.0
internals are in a MUCH better shape that those of HttpClient 2.0.x.
HttpClient 3.0 is still considered ALPHA because we cannot yet commit to
stability of its API.
> I only have a minor feature request for the preferences architecture: it
> would be nice to be able to define default HttpMethodParams per
> HttpClient instance. (i'm not sure, but you may already have taken care
> of that).
>
I believe that can be fairly easy accomplished using existing API
option 1)
========================================================
HttpClientParams params = new HttpClientParams(null);
params.setParameter("whatever", new Integer(1));
HttpClient client = new HttpClient(params);
========================================================
option 2)
========================================================
DefaultHttpParams.setHttpParamsFactory(new HttpParamsFactory()
{
public HttpParams getDefaultParams() {
HttpClientParams params = new HttpClientParams(null);
params.setParameter("whatever", new Integer(1));
return params;
}
});
HttpClient client = new HttpClient();
========================================================
Options 1 and 2 produce similar results. See which one suits your
application better.
Thanks for the feedback
Cheers,
Oleg
> Otherwise, i'm a happy customer. Thanks for all the good work!
>
> Cheers, Oliver
>
> ---------------------------------------------------------------------
> 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
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Oliver Köll <ok...@newbase.de>.
Oleg Kalnichevski wrote:
>
> Anyways, before things turn ugly, give us some feedback, pleeeeeeeeeeese
Hi Oleg,
i'm sorry, that i haven't given any feedback earlier, but i always felt,
that my understanding of HttpClient wasn't deep enough to qualify any
criticism.
The good news: i'm already using HttpClient 3.0a1 in production for some
time (i preferred it over 2.1 because of the improved Cookie handling),
and i haven't had any problems with it yet. Actually, i'm feeling that
the "alpha" categorization isn't doing the software justice :-)
I only have a minor feature request for the preferences architecture: it
would be nice to be able to define default HttpMethodParams per
HttpClient instance. (i'm not sure, but you may already have taken care
of that).
Otherwise, i'm a happy customer. Thanks for all the good work!
Cheers, Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
RE: HttpClient 3.0 is kind of done. Feedback needed
Posted by Sam Berlin <sb...@limepeer.com>.
Hi All,
Since we've finally ditched support for Java 1.1.8, we can begin to start
using modern components again (instead of our mangled HttpClient 2.0rc2).
I'll take a look at incorporating HttpClient 3.0 into an upcoming release
for LimeWire, and will give as much feedback as possible. (As well as
hopefully some patches of older various bugs I've mentioned.) You're all
always welcome to scan our bugs-searching page ( at
http://bugs.limewire.com/bugs/search.jsp ) and find bugs that occur within
the HttpClient classes. (There's a class dropdown box -- just choose one of
the classes & then search. At some point I'll go through and delete the
classes that we've purged the associated bugs.)
Thanks,
Sam
> -----Original Message-----
> From: Michael Becke [mailto:becke@u.washington.edu]
> Sent: Thursday, September 16, 2004 10:40 PM
> To: Commons HttpClient Project
> Subject: Re: HttpClient 3.0 is kind of done. Feedback needed
>
> > Another evil plan that I have been contemplating recently is to address
> > our fellow open-source developers that are known to be using HttpClient
> > (read: shamelessly spam the dev mailing lists) and ask them what they
> > think of the new 3.0 API and whether they have any migration plans. If
> > needed I am prepared to put my kevlar helmet on with a shiny red star
> > and take all the blame for this atrocity.
>
> I see no problem with this. Sounds like a good idea.
>
> > Alternatively, we can simply let things develop as their natural pace
> > and start hacking on the 4.0 branch. Having three active development
> > branches may prove too daunting, though. So I would rather see the
> > HttpClient 3.0 brought to a logical conclusion and a stable release (be
> > it late BETA, RC or FINAL), deprecate HttpClient 2.0 and then move onto
> > the 4.0.
>
> I think it's definitely too soon to make a move on 4.0. I'd prefer to
> wait until 3.0 is nearly done, and then we can forget about 2.0.
>
> Mike
>
>
> ---------------------------------------------------------------------
> 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
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Michael Becke <be...@u.washington.edu>.
> Another evil plan that I have been contemplating recently is to address
> our fellow open-source developers that are known to be using HttpClient
> (read: shamelessly spam the dev mailing lists) and ask them what they
> think of the new 3.0 API and whether they have any migration plans. If
> needed I am prepared to put my kevlar helmet on with a shiny red star
> and take all the blame for this atrocity.
I see no problem with this. Sounds like a good idea.
> Alternatively, we can simply let things develop as their natural pace
> and start hacking on the 4.0 branch. Having three active development
> branches may prove too daunting, though. So I would rather see the
> HttpClient 3.0 brought to a logical conclusion and a stable release (be
> it late BETA, RC or FINAL), deprecate HttpClient 2.0 and then move onto
> the 4.0.
I think it's definitely too soon to make a move on 4.0. I'd prefer to
wait until 3.0 is nearly done, and then we can forget about 2.0.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Oleg Kalnichevski <ol...@bearingpoint.com>.
The 3.0-alpha2 release should certainly be the first step. I would even
go so far as to announce this release be the last ALPHA release.
More visibility is definitely a must. I think we could even make use of
our new Jakarta subproject status and temporarily deploy the site
generated off the CVS HEAD at the /jakarta-site/httpclient/
Another evil plan that I have been contemplating recently is to address
our fellow open-source developers that are known to be using HttpClient
(read: shamelessly spam the dev mailing lists) and ask them what they
think of the new 3.0 API and whether they have any migration plans. If
needed I am prepared to put my kevlar helmet on with a shiny red star
and take all the blame for this atrocity.
Alternatively, we can simply let things develop as their natural pace
and start hacking on the 4.0 branch. Having three active development
branches may prove too daunting, though. So I would rather see the
HttpClient 3.0 brought to a logical conclusion and a stable release (be
it late BETA, RC or FINAL), deprecate HttpClient 2.0 and then move onto
the 4.0.
Just a bunch of (random) thoughts
Anyways, it is time we called the 3.0a2 vote
Oleg
On Thu, 2004-09-16 at 14:26, Michael Becke wrote:
> 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=&emailtyp
> > e1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailrepo
> > rter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfiel
> > dto=Now&chfieldvalue=&product=Commons&component=HttpClient&target_miles
> > 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=allwordssubstr
> > &long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_ty
> > 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
Re: HttpClient 3.0 is kind of done. Feedback needed
Posted by Michael Becke <be...@u.washington.edu>.
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=&emailtyp
> e1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailrepo
> rter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfiel
> dto=Now&chfieldvalue=&product=Commons&component=HttpClient&target_miles
> 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=allwordssubstr
> &long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_ty
> 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