Return-Path: Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 70791 invoked from network); 28 Jul 2003 13:26:59 -0000 Received: from smtp.bearingpoint.com (HELO KCCXOEX11.corp.kpmgconsulting.com) (57.80.136.23) by daedalus.apache.org with SMTP; 28 Jul 2003 13:26:59 -0000 Received: from kccxoex06.corp.kpmgconsulting.com ([10.98.3.31]) by KCCXOEX11.corp.kpmgconsulting.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 28 Jul 2003 13:24:02 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: FW: Commons-HttpClient conflict with WebDAVClient Date: Mon, 28 Jul 2003 14:26:58 +0100 Message-ID: <825BF35A92B3F0479CC164ECBBE9376E0DE5D8@kccxoex06.corp.kpmgconsulting.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FW: Commons-HttpClient conflict with WebDAVClient Thread-Index: AcNVAhSdG0ubUxMfQ/Ga63kK2haRVQAB9GrQ From: "Kalnichevski, Oleg" To: "Commons HttpClient Project" X-OriginalArrivalTime: 28 Jul 2003 13:24:02.0234 (UTC) FILETIME=[82B3F9A0:01C3550B] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Eric, Of course, the patch can be rolled back. Alternatively we can leave = getResponseContentLength() method as is, and introduce an additional = method that serve similar function but returns long, not int. But the whole point is that I really can't understand why Slide folks = cannot just use stable 2.0 branch. At the end of the day back in = February we decided to release 2.0 with the sub-optimal API primarily in = order to keep Slide folks happy (even though we were still formally in = alpha phase). And now what? Is history about to repeat itself? Is there any particular reason for Slide to use CVS HEAD? =20 Oleg -----Original Message----- From: Eric Johnson [mailto:eric@tibco.com] Sent: Monday, July 28, 2003 14:16 To: Commons HttpClient Project Subject: Re: FW: Commons-HttpClient conflict with WebDAVClient Oleg, Actually, I'm expecting that the redirect fix will probably not change=20 the way that webdavclient.jar works with HttpClient. I think the=20 redirect fix will only be a problem for some uses of the HttpClient = library. I would appreciate the change of the getResponseContentLength() back to=20 its previous return value. I think it would be worth revisiting that=20 decision. How about getResponseContentLength() and getResponseLength()? -Eric. Kalnichevski, Oleg wrote: >>There's also the int/long change for getResponseContentLength() which=20 >>causes the compile to break on one or the other. Perhaps we should=20 >>rethink the decision to just change that return type? >> =20 >> > >And are we going to do when the redirect fix is implemented? People = should not expect Slide to compile against CVS HEAD until 2.1 (or 3.0) = APIs are frozen.=20 > >Evil Comrade Oleg > >--------------------------------------------------------------------- >To unsubscribe, e-mail: = commons-httpclient-dev-unsubscribe@jakarta.apache.org >For additional commands, e-mail: = commons-httpclient-dev-help@jakarta.apache.org > > > > =20 > --------------------------------------------------------------------- To unsubscribe, e-mail: = commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: = commons-httpclient-dev-help@jakarta.apache.org