Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: 217.158.94.220 is neither permitted nor
 denied by domain of t.p.ellison@gmail.com)
Message-ID: <43044056.7070303@gmail.com>
Date: Thu, 18 Aug 2005 09:01:26 +0100
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [arch] Modular JVM component diagram
References: <20050816174543.97012.qmail@web41204.mail.yahoo.com>
In-Reply-To: <20050816174543.97012.qmail@web41204.mail.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Ricardo,

Do you intend to put some words to your attachment?  I took a look but
it didn't make much sense to me without understanding the notations and
colors you adopted.

But... it did cause me to go back and re-read Jon's original
architecture proposal.  I broadly agree with the proposal, and have the
following minor comments:

 - Can we avoid calling the class library project "classpath", unless we
specifically mean GNU Classpath?

 - I'm pleased to see the "development facilities" subproject taking a
major role; however, the proposal says that the development facilites
should be "stripped from the build for non-development releases".  I
suggest that we design the trace / debug facilities in such a way that
they can be left in all builds, and enabled at different levels
appropriate to the usage requirements from development to end-user.

 - The claim is that "The main Harmony project in terms of volume is
likely the JVM project" -- if we are on the hook to do a classlibrary
implementation that will dwarf the VM in terms of volume ;-/

- Although not shown in the diagram, I'm assuming that the core
interpreter comes under the Runtime Project in JVM.

 - The "VM Core Sub-components" that dims added is a good list of things
that will be addressed in the vm-core.  Some of these have a natural
grouping.

 - I'd vote that the "J2SDK Toolkit" be predominantly written in Java
and avoid the requirement for the CTL.

Regards,
Tim


Ricardo Morin wrote:
> Hi All:
> 
> In order to continue refining the discussions on JVM
> modularity, I have added a component diagram to the
> HarmonyArchitecture Wiki page. The diagram drills down
> on the "Modular Structure JVM Components" section by
> depicting the major components and interfaces. I
> propose discussing the suggested structure and then
> proceed to describe and define the components and
> interfaces in more detail, based on our discussions.
> 
> http://wiki.apache.org/harmony/HarmonyArchitecture
> 
> http://wiki.apache.org/harmony-data/attachments/HarmonyArchitecture/attachments/ModularJVM.jpg
> 
> Comments? Ideas?
> 
> Thank you,
> 
> Ricardo
> 
> ____________________________________________________
> Start your day with Yahoo! - make it your home page 
> http://www.yahoo.com/r/hs 
>  
> 

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.