<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Networking &#8211; Sockets &amp; RMI</title>
	<atom:link href="http://bhuvans.wordpress.com/2006/08/17/networking-sockets-rmi/feed/" rel="self" type="application/rss+xml" />
	<link>http://bhuvans.wordpress.com/2006/08/17/networking-sockets-rmi/</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 11:05:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: suresh</title>
		<link>http://bhuvans.wordpress.com/2006/08/17/networking-sockets-rmi/#comment-67813</link>
		<dc:creator><![CDATA[suresh]]></dc:creator>
		<pubDate>Tue, 19 Jun 2012 02:42:05 +0000</pubDate>
		<guid isPermaLink="false">https://bhuvans.wordpress.com/2006/08/17/networking-sockets-rmi/#comment-67813</guid>
		<description><![CDATA[&lt;a href=&quot;http://www.interview-topics.blogspot.com&quot; rel=&quot;nofollow&quot;&gt;Interview Questions and answers&lt;/a&gt; seems to be useful...tq :)]]></description>
		<content:encoded><![CDATA[<p><a href="http://www.interview-topics.blogspot.com" rel="nofollow">Interview Questions and answers</a> seems to be useful&#8230;tq <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mosele</title>
		<link>http://bhuvans.wordpress.com/2006/08/17/networking-sockets-rmi/#comment-57558</link>
		<dc:creator><![CDATA[mosele]]></dc:creator>
		<pubDate>Thu, 01 Oct 2009 21:23:20 +0000</pubDate>
		<guid isPermaLink="false">https://bhuvans.wordpress.com/2006/08/17/networking-sockets-rmi/#comment-57558</guid>
		<description><![CDATA[RMI Programming

http://patriot.net/~tvalesky/easyrmi.html

a review by Lan Chen

 

This article gives a very simple and good example of how to make a RMI program in JAVA. It provide the basic structure of a RMI program for beginners , so they can imitate the structure and get started. However, since RMI is one of the complex system i n java. It required a good understanding of RPC in order to understand RMI.

How java’s RMI related to Distributed System
Distributed system required tasks running in different address space and virtual machines. In java, there are two method to do this. First is socket. But sockets require client and server to work at application level protocols and message exchanging, w hich requires much detail work. The other is RMI. RMI is based on RPC. RPC abstracts the details to the level of a procedure call. The difference between two is RMI is for object system.

How RMI works
As introduced in the article, there is an simple client-server example

Client side: Client has at least two class. One is the client’s interface for accessing the server’s method. There is no implementation in the interface, just give out the signature.

The other is client program. It uses &quot;lookup&quot; to find the remote object by name in the server’s registry. Then it can access server object through the interface.

Server side: Server should first have a class to implement the interface. Then server also need a program to create an instance of the implementation.

More comparison for RPC and RMI
The basic structure of RPC is as follows:



In java’s RMI, the client access the interface. The rmic complier will automatic generate the client stub and server skeleton. And programmer does not need to consider the communication details. The main structure is nearly same as the above figure, ex cept for its OOP feature.

 

To conclude, the article is merely a simple introduction for RMI programming. Because of the close relationship between RPC and RMI, to learn RMI would also give a more down-to-ground understanding on how the RPC can be implemented. So I think it is r eally worth to know a little bit of RMI as a supplement of this course.]]></description>
		<content:encoded><![CDATA[<p>RMI Programming</p>
<p><a href="http://patriot.net/~tvalesky/easyrmi.html" rel="nofollow">http://patriot.net/~tvalesky/easyrmi.html</a></p>
<p>a review by Lan Chen</p>
<p>This article gives a very simple and good example of how to make a RMI program in JAVA. It provide the basic structure of a RMI program for beginners , so they can imitate the structure and get started. However, since RMI is one of the complex system i n java. It required a good understanding of RPC in order to understand RMI.</p>
<p>How java’s RMI related to Distributed System<br />
Distributed system required tasks running in different address space and virtual machines. In java, there are two method to do this. First is socket. But sockets require client and server to work at application level protocols and message exchanging, w hich requires much detail work. The other is RMI. RMI is based on RPC. RPC abstracts the details to the level of a procedure call. The difference between two is RMI is for object system.</p>
<p>How RMI works<br />
As introduced in the article, there is an simple client-server example</p>
<p>Client side: Client has at least two class. One is the client’s interface for accessing the server’s method. There is no implementation in the interface, just give out the signature.</p>
<p>The other is client program. It uses &#8220;lookup&#8221; to find the remote object by name in the server’s registry. Then it can access server object through the interface.</p>
<p>Server side: Server should first have a class to implement the interface. Then server also need a program to create an instance of the implementation.</p>
<p>More comparison for RPC and RMI<br />
The basic structure of RPC is as follows:</p>
<p>In java’s RMI, the client access the interface. The rmic complier will automatic generate the client stub and server skeleton. And programmer does not need to consider the communication details. The main structure is nearly same as the above figure, ex cept for its OOP feature.</p>
<p>To conclude, the article is merely a simple introduction for RMI programming. Because of the close relationship between RPC and RMI, to learn RMI would also give a more down-to-ground understanding on how the RPC can be implemented. So I think it is r eally worth to know a little bit of RMI as a supplement of this course.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
