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.
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 <[EMAIL PROTECTED]> 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
