Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 3889 invoked from network); 20 Apr 2006 13:46:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Apr 2006 13:46:54 -0000 Received: (qmail 38558 invoked by uid 500); 20 Apr 2006 13:46:38 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 38490 invoked by uid 500); 20 Apr 2006 13:46:37 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 38479 invoked by uid 99); 20 Apr 2006 13:46:37 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2006 06:46:37 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [134.134.136.20] (HELO orsmga101-1.jf.intel.com) (134.134.136.20) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2006 06:46:36 -0700 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101-1.jf.intel.com with ESMTP; 20 Apr 2006 06:46:16 -0700 Received: from fmsmsx331.fm.intel.com (HELO fmsmsx331.amr.corp.intel.com) ([132.233.42.156]) by orsmga001.jf.intel.com with ESMTP; 20 Apr 2006 06:46:16 -0700 X-IronPort-AV: i="4.04,141,1144047600"; d="scan'208"; a="25535585:sNHT84880474" Received: from fmsmsx311.amr.corp.intel.com ([132.233.42.214]) by fmsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 20 Apr 2006 06:46:15 -0700 Received: from mssmsx402.ccr.corp.intel.com ([10.125.2.12]) by fmsmsx311.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 20 Apr 2006 06:46:15 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Contribution of RMI framework Date: Thu, 20 Apr 2006 17:46:07 +0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Contribution of RMI framework Thread-Index: AcZj9pweBvYpwtTMSqGMzZBhnEQHqgAig9QQ From: "Zakharov, Vasily M" To: X-OriginalArrivalTime: 20 Apr 2006 13:46:15.0101 (UTC) FILETIME=[CB0016D0:01C66480] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Daniel, Regretfully, we have no specific top level design documentation. However, the general design of the RMI package is described rather well in public sources. For example, you could check the "Java RMI: Remote Method Invocation" book by Troy Bryan Downing or Sun's jGuru RMI course at http://java.sun.com/developer/onlineTraining/rmi/RMI.html Vasily -----Original Message----- From: Daniel Gandara [mailto:danielgandara@neosur.com]=20 Sent: Thursday, April 20, 2006 1:17 AM To: harmony-dev@incubator.apache.org Subject: Re: Contribution of RMI framework Vasily,=20 I'm reviewing your implementation, I believe there is a lot to learn about other's solution to the same problem :) and I'm wondering=20 if you can send me some top level design documentation about your=20 package. Thanks, Daniel PS: if you happen to need it you can find more info about our design here http://www.itc.unc.edu.ar/javadev/rmi/architecture.html ----- Original Message -----=20 From: "Daniel Gandara" To: Sent: Monday, April 17, 2006 12:05 PM Subject: Re: Contribution of RMI framework >I completelly agree with Vasily, doing test and performance analysis=20 > on RMI is not a trivial task; I'll coordinate with him the best way to > compare the packages. >=20 > Daniel >=20 > ----- Original Message -----=20 > From: "Zakharov, Vasily M" > To: > Sent: Friday, April 14, 2006 1:17 PM > Subject: RE: Contribution of RMI framework >=20 >=20 > Hi, Mikhail, >=20 > Regretfully, the method-to-method comparison would hardly be effective > with RMI, as it's a highly integrated component. >=20 > 80% of implementation is hidden in non-public API, and some components > (e. g. RMIC) have no public API at all. So it's hard to plug just one > public method from one implementation to another without modifying > non-public code - and non-public code could have (and probably does > have) very different structure in different implementations. >=20 > What we really can do is try to run both these implementations and > compare them for conformance to the specification, compatibility with > reference implementation, maybe stability, performance, visual code > quality etc. I'm now planning to do some of these, so we'd get some > results pretty soon. >=20 > Vasily >=20 >=20 > -----Original Message----- > From: Mikhail Loenko [mailto:mloenko@gmail.com]=20 > Sent: Friday, April 14, 2006 7:53 AM > To: harmony-dev@incubator.apache.org > Subject: Re: Contribution of RMI framework >=20 > I think we need compare contributions method by method to assemble > the best classlib >=20 > Thanks, > Mikhail >=20 > 2006/4/14, Daniel Gandara : >> Vasily, >> good to know that there is someone out there who has also >> been working on rmi; I believe we'll have a lot to share and discuss >> about it. >> >> Thanks, >> >> Daniel >> >> ----- Original Message ----- >> From: "Zakharov, Vasily M" >> To: >> Sent: Wednesday, April 12, 2006 9:53 PM >> Subject: Contribution of RMI framework >> >> >> Hi, all, >> >> I would like to announce the next code contribution to Harmony project >> on >> behalf of Intel corporation. This contribution contains the >> implementation >> of RMI framework. >> >> The archive with this contribution can be found at: >> >> http://issues.apache.org/jira/browse/HARMONY-337 >> >> The Remote Method Invocation (RMI) framework enables an object in one >> virtual machine to call methods of an object in another one, to create >> applications distributed on various Java virtual machines on the same >> or different hosts. >> >> For more information please see the documentation contained in the >> bundle. >> >> The code is a result of efforts of Intel Middleware Product Division >> team. >> One should be able to run this code with a 1.4+ compatible JRE/VM (was >> tested using commercial VMs). No classes require special support from >> the VM. >> All code is pure Java. The implementation is done according to Java > 1.4 >> specification of RMI. >> >> The archive contains the README file that explains the building and >> running >> process for this code. If any additional comments or clarifications > are >> needed, feel free to contact me. I will be happy to answer all > questions >> about this contribution and to participate in its further >> development/maintenance and integration into Harmony. >> >> Vasily Zakharov >> Intel Middleware Product Division >> >=20 > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org > For additional commands, e-mail: harmony-dev-help@incubator.apache.org >=20 >=20 >=20 > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org > For additional commands, e-mail: harmony-dev-help@incubator.apache.org > --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org