Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 69318 invoked from network); 10 Aug 2000 18:33:01 -0000 Received: from dnai-216-15-97-206.cust.dnai.com (HELO kali.betaversion.org) (216.15.97.206) by locus.apache.org with SMTP; 10 Aug 2000 18:33:01 -0000 Received: from apache.org (sun.betaversion.org [192.168.1.4] (may be forged)) by kali.betaversion.org (8.9.3+Sun/8.9.3) with ESMTP id LAA04656 for ; Thu, 10 Aug 2000 11:32:58 -0700 (PDT) Message-ID: <3992F5FD.66D552CE@apache.org> Date: Thu, 10 Aug 2000 11:35:41 -0700 From: "Pier P. Fumagalli" Reply-To: pier@betaversion.org Organization: Apache Software Foundation X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: [PROPOSALS] Three Proposals for Development of Tomcat 4.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N "yhs@mimic.onesourcecorp.com" wrote: > > ugh. please please maintain JDK 1.1 compatibility for runtime at > least. compiling is ok with JDK 1.2 but JDK 1.1 is a lot more stable for > high volume traffic at runtime. ive seen suns JDK 1.2.2 lock up under high > loads...1.1 doesnt. dropping 1.1 compatibility before 1.2 becomes stable > enough for production use is IMHO a really *bad* idea. I don't agree on maintaining JDK 1.1 compatibility... I believe it's now time to give the good old Platform 1.1 a sound kick in the butt and start working on Platform 2. In my personal experience I've never seen JDK 1.2.2 to lock, on both the operating systems I use (Windo$H and Solaris), actually never had the lightest problem. On what O/S did you see it happen? Pier BTW, Check your computer's date/time... Your message was dated Mon, 6 Jan 1997 19:01:52 -0500 (EST)