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:[EMAIL PROTECTED] 
Sent: Thursday, April 20, 2006 1:17 AM
To: [email protected]
Subject: Re: Contribution of RMI framework

Vasily, 

    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 
if you can send me some top level design documentation about your 
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 ----- 
From: "Daniel Gandara" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, April 17, 2006 12:05 PM
Subject: Re: Contribution of RMI framework


>I completelly agree with Vasily, doing test and performance analysis 
> on RMI is not a trivial task; I'll coordinate with him the best way to

> compare the packages.
> 
> Daniel
> 
> ----- Original Message ----- 
> From: "Zakharov, Vasily M" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Friday, April 14, 2006 1:17 PM
> Subject: RE: Contribution of RMI framework
> 
> 
> Hi, Mikhail,
> 
> Regretfully, the method-to-method comparison would hardly be effective
> with RMI, as it's a highly integrated component.
> 
> 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.
> 
> 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.
> 
> Vasily
> 
> 
> -----Original Message-----
> From: Mikhail Loenko [mailto:[EMAIL PROTECTED] 
> Sent: Friday, April 14, 2006 7:53 AM
> To: [email protected]
> Subject: Re: Contribution of RMI framework
> 
> I think we need compare contributions method by method to assemble
> the best classlib
> 
> Thanks,
> Mikhail
> 
> 2006/4/14, Daniel Gandara <[EMAIL PROTECTED]>:
>> 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" <[EMAIL PROTECTED]>
>> To: <[email protected]>
>> 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
>>
> 
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to