[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    developer.kde.org/documentation/other
From:       Waldo Bastian <bastian () kde ! org>
Date:       2004-02-05 14:08:49
Message-ID: 20040205140849.84FDA9914 () office ! kde ! org
[Download RAW message or body]

CVS commit by waba: 

Local procedure calls and remote procedure calls are not the same
http://www.sunlabs.com/techrep/1994/abstract-29.html


  M +33 -1     rpc-technologies.html   1.3


--- developer.kde.org/documentation/other/rpc-technologies.html  #1.2:1.3
@@ -28,4 +28,5 @@
 <i>Thanks to Tim Jansen for his very excellent hints, as well as the guys
 on kde-devel(at)kde.org</i>
+
 <h2>Overview</h2>
 <p>This document aims to be a short guide for the current RPC (Remote procedure
@@ -33,4 +34,5 @@
 your project. You might skip to the section you are most interested in, since
 the first few items will be about RPC in general.</p>
+
 <h2>What is RPC? And why should I use that?</h2>
 At first, you need to know that it is sometimes necessary to create client/server
@@ -39,4 +41,5 @@
 RPC services and then you can begin choosing the RPC solution which fits
 best to your project.
+
 <h3>The client/server concepts</h3>
 <p>RPC is generally used in client/server concepts. This might sound overblown,
@@ -53,4 +56,5 @@
 necessarly includes that bi-directional communications, but often it is used
 to do status-checks of the communication.</p>
+
 <h3>So what is an RPC technology?</h3>
 <p>An RPC technology is a standarized way of exchanging data using a single
@@ -63,4 +67,5 @@
 is supported (either as library or implemented in the application itself).
 Basically spoken, the HTTP protocol is a very specialized RPC technology.</p>
+
 <h3>When shouldn't you use RPC technologies?</h3>
 If you use the KDE libraries and don't want to develop applications that
@@ -68,4 +73,5 @@
 examples which usually don't RFC technologies are: Text editors, Graphic
 Applications, Word Processors and such.
+
 <h3>When should you use RPC technologies?</h3>
 You should use RPC technologies if you are going to write standards-oriented,
@@ -93,6 +99,32 @@
 Spectrum</a>)</li>
   <li>Applications that want to communicate with each other over the network,
-and where it's not necessary to re-implement new propitary protocols</li>
+and where it's not necessary to re-implement new proprietary protocols</li>
 </ul>
+
+<h3>Local procedure calls and remote procedure calls are not the same</h3>
+<p>Whatever technology you use, local procedure calls and remote procedure calls are
+not the same, no matter how seamless and transparant they appear. It is important to recognize
+the differences and take these differences and their implications serious.</p>
+<p>The following white paper provides a good overview of the issues:<br>
+<blockquote>
+<i>"We argue that objects that interact in a distributed system need to be dealt with in ways that
+are intrinsically different from objects that interact in a single address space. These
+differences are required because distributed systems require that the programmer be aware
+of latency, have a different model of memory access, and take into account issues of
+concurrency and partial failure.<br><br>
+
+We look at a number of distributed systems that have attempted to paper over the distinction
+between local and remote objects, and show that such systems fail to support basic requirements
+of robustness and reliability. These failures have been masked in the past by the small size of
+the distributed systems that have been built. In the enterprise-wide distributed systems foreseen
+in the near future, however, such a masking will be impossible.<br><br>
+
+We conclude by discussing what is required of both systems-level and application-level programmers
+and designers if one is to take distribution seriously."</i>
+</blockquote>
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://www.sunlabs.com/techrep/1994/abstract-29.html">
+http://www.sunlabs.com/techrep/1994/abstract-29.html</a>
+</p>
+
 <h2>Simple textual comparisation</h2>
 <p>This is a simple textual comparisation I've posted to the kde developer


[prev in list] [next in list] [prev in thread] [next in thread]