Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 50707 invoked from network); 22 Feb 2008 11:22:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2008 11:22:59 -0000 Received: (qmail 48720 invoked by uid 500); 22 Feb 2008 11:22:53 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 48190 invoked by uid 500); 22 Feb 2008 11:22:52 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 48181 invoked by uid 99); 22 Feb 2008 11:22:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 03:22:52 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of firepure@gmail.com designates 64.233.166.179 as permitted sender) Received: from [64.233.166.179] (HELO py-out-1112.google.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 11:22:19 +0000 Received: by py-out-1112.google.com with SMTP id a25so496843pyi.13 for ; Fri, 22 Feb 2008 03:22:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=6QV/4I/IBY5MtjW5N51wAg7NWSgpFUdNuZRxirj9anQ=; b=vPupu6qTq4oz42KTHvZIePGm/ZVigZ+zBYUCzDls3WAz7gnTABSP9/dQlsZQKFVKNApjYGlOViEwz7DESjEo2+ihFg51PoORlrwWnMfUGmfc+8zUhk39nJEFsgAJKmM9Oocmw/kAaPWUsdBPYmDeA/1r3WxO2hvURF19zxd9Po8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XpmLjoug3dqn/sjj+33j4yPR0TmRpZF4bz/W7hux7mE1070+av8SioWrNFn4vbF18K6QxX1sHWj+8Don/6Y3n3dzkl96KMPcC7BwXzTqcMWI4b2EeDIjyORzBNyfEjKvoihIZPOpTVVjpoheUGyvMDdcLnDuWsJz0qczMjjDewM= Received: by 10.65.139.9 with SMTP id r9mr22083783qbn.71.1203679347728; Fri, 22 Feb 2008 03:22:27 -0800 (PST) Received: by 10.65.251.12 with HTTP; Fri, 22 Feb 2008 03:22:27 -0800 (PST) Message-ID: <5c8e69f0802220322g18d30f33k41aede96e8dbb9a9@mail.gmail.com> Date: Fri, 22 Feb 2008 19:22:27 +0800 From: "Jimmy,Jing Lv" To: dev@harmony.apache.org Subject: Re: [JDKTools][JDWP]Let's start JDWP java6 updating In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5c8e69f0802211930r1f27c40fwd0c3cbfa8aa9075a@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, 2008/2/22, Alexei Fedotov : > Jimmy, > > I fully support your idea, but cannot follow the discussion fully. The > old thread mostly discussed a shared memory protocol, didn't it? This > thread no longer mentions a shared memory, but discusses an API update > instead. May be all these things are parts of the whole picture, but > the picture slips out of my mind. I would suggest being merciful to my > google-weakened brain and write some justifications of the decision > taken. > Yes, I never forget shared memory, but it seems we need more information of that (according to the conclusion of last discussion). However java6 updating is easier to work on and we've got all information on java spec, as a result, IMO, we'd better start from the easy beginning, and leave hard work alone until we find some other way to resolve it, do you think so? :) (Maybe someone already has a plan on it :) BTW, as today is friday, have a nice weekend :) > For example, I believe Mikhail L. justification: "I don't think that > time and efforts are an issue. The time flies when you are having fun > :)" is quite explanatory. Or you may come up with something more > rational. > > Thanks. > > > On Fri, Feb 22, 2008 at 6:30 AM, Jimmy,Jing Lv wrote: > > Hi All, > > > > As discussed before, we can start JDWP updating and improving. > > IMHO, let's start from the easiest way, updating to java 6. > > My proposal is: > > 1. Setup a branch of JDKTools for java6 in harmony repository > > 2. add/improve JDWP functions into java6 level. As the main updating > > for java6 JDWP is about JDWP-protocol, it seems no much effect on VM > > and debugger. > > > > As M5 freeze will be done at the end of this week, may start > > from next week on. Any comments/suggestions/Volunteers? Thanks! > > > > -- > > > > Best Regards! > > > > Jimmy, Jing Lv > > China Software Development Lab, IBM > > > > > > > -- > With best regards, > > Alexei > -- Best Regards! Jimmy, Jing Lv China Software Development Lab, IBM