Return-Path: 
 <dev-return-32841-apmail-avalon-dev-archive=avalon.apache.org@avalon.apache.org>
Delivered-To: apmail-avalon-dev-archive@www.apache.org
Received: (qmail 25011 invoked from network); 13 Jul 2004 18:17:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 13 Jul 2004 18:17:52 -0000
Received: (qmail 95102 invoked by uid 500); 13 Jul 2004 18:17:41 -0000
Delivered-To: apmail-avalon-dev-archive@avalon.apache.org
Received: (qmail 95045 invoked by uid 500); 13 Jul 2004 18:17:40 -0000
Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@avalon.apache.org>
List-Subscribe: <mailto:dev-subscribe@avalon.apache.org>
List-Help: <mailto:dev-help@avalon.apache.org>
List-Post: <mailto:dev@avalon.apache.org>
List-Id: "Avalon Developers List" <dev.avalon.apache.org>
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Delivered-To: mailing list dev@avalon.apache.org
Received: (qmail 95025 invoked by uid 99); 13 Jul 2004 18:17:40 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [170.190.17.220] (HELO jismsg1.nashville.org) (170.190.17.220)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 13 Jul 2004 11:17:37 -0700
Received: by jismsg1.nashville.org with Internet Mail Service (5.5.2653.19)
	id <LP8FM2BF>; Tue, 13 Jul 2004 13:20:45 -0500
Message-ID: 
 <D78EC74BB0600241A3EE06FA8E0FEA9F06710C7E@jismsg01.jis.nashville.org>
From: "Bennett, Timothy (JIS/Applications)"
	 <TimothyBennett@jis.nashville.org>
To: 'Avalon Developers List' <dev@avalon.apache.org>
Subject: RE: Technical Concerns over AF4.2
Date: Tue, 13 Jul 2004 13:17:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com] 
> Sent: Tuesday, July 13, 2004 12:59 PM
> To: Avalon Developers List
> Subject: RE: Technical Concerns over AF4.2
> 
> 
> > here's how we envision its use in the new Avalon
> 
> Who is "we"?  If you are intending to drop compatibility with 
> other Avalon products such as Excalibur, etc., I suggest that 
> we move Frameworks from the stewardship of Avalon to Excalibur.
> 

Who's said anything about any intention to drop compatibility with anyone?
Frameworks and specifications mature.  If you want to take advantage of NIO,
you move your application to JRE 1.4.  If you don't need it/want it because
you don't have time/desire to assume the *risk*, you stay compatible with
JRE 1.3.  I fail to see how the evolution of the Avalon framework and
specification is any different?

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