Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: commits@harmony.apache.org
Date: Wed, 25 Mar 2009 00:39:12 -0000
Message-ID: <20090325003912.7763.82169@aurora.apache.org>
Subject: [Harmony Wiki] Update of "Google Summer Of Code 2009 Projects
 Proposals" by
 XiaoFeng Li

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Harmony Wiki" for change notification.

The following page has been changed by XiaoFeng Li:
http://wiki.apache.org/harmony/Google_Summer_Of_Code_2009_Projects_Proposals

------------------------------------------------------------------------------
  || '''Possible Mentors''' || Xiao-Feng Li (committer)||
  || '''Status''' || Unassigned ||
  
+ || '''Subject ID''' || ''harmony-GC-1'' ||
+ || '''Title''' || ''' Implement WeakReference support in Harmony concurrent GC ''' ||
+ || '''ASF Project''' || Apache Harmony http://harmony.apache.org ||
+ || '''Keywords''' || Harmony, concurrent GC, weak reference ||
+ || '''Description''' || Harmony already has a concurrent GC (called Tick, with three concurrent GC algorithms). It runs well with standard benchmarks. The only remaining unfinished feature is WeakReference support . Weakly referenced object (i.e., referent) is accessed through get() interface. That means, get() operation can make a weakly reachable referent strongly reachable. During concurrent collection, the system must monitor the get() operation to catch this change of reachability, otherwise the referent could be reclaimed. This project also includes to integrate the WeakReference processing with Finalization process. Other optimizations in Tick are also desirable, such as to reduce the amount of floating garbage. ||
+ || '''Possible Mentors''' || Xiao-Feng Li (committer)||
+ || '''Status''' || Unassigned ||
+