Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 44281 invoked from network); 23 Sep 2003 20:53:35 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 23 Sep 2003 20:53:35 -0000 Received: (qmail 32796 invoked by uid 500); 23 Sep 2003 20:53:21 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 32768 invoked by uid 500); 23 Sep 2003 20:53:20 -0000 Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Commons HttpClient Project" Reply-To: "Commons HttpClient Project" Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 32753 invoked from network); 23 Sep 2003 20:53:20 -0000 Received: from unknown (HELO mail1.bluewin.ch) (195.186.1.74) by daedalus.apache.org with SMTP; 23 Sep 2003 20:53:20 -0000 Received: from fatboy (81.62.182.70) by mail1.bluewin.ch (Bluewin AG 7.0.020) id 3F57033E002373C0 for commons-httpclient-dev@jakarta.apache.org; Tue, 23 Sep 2003 20:53:25 +0000 Subject: Re: JDK 1.1.8 problems From: Oleg Kalnichevski Reply-To: olegk@apache.org To: Commons HttpClient Project In-Reply-To: <3F70AA37.5000002@u.washington.edu> References: <1064347795.2319.14.camel@kczrh-okt22.corp.bearingpoint.com> <3F70AA37.5000002@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1064350402.2319.23.camel@kczrh-okt22.corp.bearingpoint.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Tue, 23 Sep 2003 22:53:22 +0200 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 2003-09-23 at 22:16, Michael Becke wrote: > How much work was involved in the port? It took me just a few hours, but I have to say I know quite a bit about HttpClient's internals. > Is it something that will be > maintainable? > This year release is going to be the last one with JRE 1.1 support as far as my application is concerned. I doubt I would actively maintain the port myself. Unless someone else steps in, the port would be pretty much unmaintainable. Oleg > Mike > > Oleg Kalnichevski wrote: > > Folks, > > I just finished porting HttpClient 2.0rc1 to JRE 1.1. If there's enough > > interest I'll put a semi-official HttpClient fork on SourceForge.org for > > those who, like me ,still have to support Java 1.1 platforms. > > Any strong opinions for or against it? > > > > Cheers > > > > Oleg > > > > > > On Thu, 2003-08-14 at 21:36, David.Cowan@apcc.com wrote: > > > >>Not extremely urgent, but I would definately be interested in using it when > >>you make it available. > >> > >> > >> > >> > >> > >> "Kalnichevski, Oleg" > >> >> point.com> > >> cc: > >> 08/14/2003 10:45 AM Subject: RE: JDK 1.1.8 problems > >> Please respond to "Commons > >> HttpClient Project" > >> > >> > >> > >> > >> > >> > >>Odi, I was thinking about it. I do not mind making my Java 1.1 fork > >>available. The trouble is that it is quite outdated. There is a very high > >>likelihood that I will get a chance to update it before December this year, > >>but I would like to wait as long as I can in order to base it on one of our > >>2.1-beta releases (hopefully coming out by that time). As far as I am > >>concerned 2.0 is already a legacy platform. > >> > >>David, let me know how urgently you need a Java 1.1 compatible version of > >>HttpClient. If waiting is an option, I'll happily share my HttpClient fork > >>with you as soon as I get a chance to bring it up to date > >> > >>Oleg > >> > >>-----Original Message----- > >>From: Ortwin Gl�ck [mailto:ortwin.glueck@nose.ch] > >>Sent: Thursday, August 14, 2003 5:37 PM > >>To: Commons HttpClient Project > >>Subject: Re: JDK 1.1.8 problems > >> > >> > >>Oleg, > >> > >>just an idea: maybe you can open a sourceforge.net project with the > >>1.1.8 version of HttpClient and share it with David. Should be > >>compatible with the Apache License but still distinguish it from the > >>'official' build. > >> > >>Odi > >> > >>Kalnichevski, Oleg wrote: > >> > >> > >>>If you are able to sleep comfortably having shipped such a library to > >>>your clients, good for you. I am not. Facing similar dilemma a year > >>>ago I ended up forking HttpClient. > >>> > >>>Oleg > >> > >> > >> > >> > >> > >>--------------------------------------------------------------------- > >>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 > >> > >> > >> > >> > >> > >> > >>--------------------------------------------------------------------- > >>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 > > > > > --------------------------------------------------------------------- > 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