<div>Obviously it is tricky to compare since RMI is running over TCP anyway, but the following provides some interesting information regarding differences in bandwidth usage and response times between the two approaches:</div>
<div> </div>
<div><a href="http://lisas.de/~adrian/master/rmi.pdf">http://lisas.de/~adrian/master/rmi.pdf</a></div>
<div> </div>
<div>Also, interesting bit at the end of this article regarding sockets programming with serialisation against RMI:</div>
<div> </div>
<div><a href="http://java.sun.com/developer/technicalArticles/ALT/sockets/">http://java.sun.com/developer/technicalArticles/ALT/sockets/</a></div>
<div> </div>
<div>RMI would be used in a Java only environment and presents a more simple environment for developers who are not familiar with sockets programming. It is automatically thread safe, whereas if you were doing sockets programming, you'd have to do this yourself.
</div>
<div> </div>
<div>As in the first URL, I would definitely recommend the use of something like Ethereal/tcpdump to look at the packets and see exactly what traffic is going backwards and forwards -- especially if this is the level at which you are investigating how connections are established/carried out/terminated.
</div>
<div> </div>
<div>Hope this helps.</div>
<div>Darren.</div>
<div> </div>
<div><br><br> </div>
<div><span class="gmail_quote">On 12/14/05, <b class="gmail_sendername">Stephen Elliott</b> <<a href="mailto:techweb@ntlworld.com">techweb@ntlworld.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>Thanks for everyones help with the Java programs I was writing.<br><br>I now need to explain in my report the differences between RMI and TCP
<br>Sockets with regards to the following.<br><br>How connections are establisbed<br>How conversations are carried out<br>How connections are terminated<br><br>So far I have came up with the fact that RMI is a tidy but slower way of
<br>implementing this. Hides most from the user. TCP Sockets are the DIY<br>approach and is faster and programmer has more control.<br><br>In TCP you need to open and close sockets which you son't need to do in RMI<br>as you are calling a remote method.
<br><br>Are there any additional points that anyone can think of?<br><br>Many Thanks<br>Steve...<br>--<br>No virus found in this outgoing message.<br>Checked by AVG Free Edition.<br>Version: 7.1.371 / Virus Database: 267.13.13
/199 - Release Date: 13/12/2005<br><br><br>_______________________________________________<br>Beds mailing list<br><a href="mailto:Beds@mailman.lug.org.uk">Beds@mailman.lug.org.uk</a><br><a href="http://mailman.lug.org.uk/mailman/listinfo/beds">
http://mailman.lug.org.uk/mailman/listinfo/beds</a><br></blockquote></div><br>