Distributed programming: Difference between revisions

Revision as of 02:24, 10 July 2005

Revision as of 18:54, 29 July 2005

Line 3:

Nearly any [[programming language]] that has access to the full [[hardware]] of the system could handle distributed programming given enough time and code. [[Remote procedure call]]s distribute [[operating system]] commands over a network connection. Systems like [[CORBA]], Microsoft [[DCOM |D/COM]], [[Java RMI]] and others, try to map [[object oriented]] design to the network. Loosely coupled systems that communicate through intermediate documents that are typically human readable are [[XML]], [[HTML]], [[SGML]], [[X.500]], and [[EDI]].

Distributed programming typically falls into one of several basic architectures or categories: [[Client-server]], [[Three-tier (computing)|3-tier architecture]], [[Multitier architecture|N-tier architecture]], [[Distributed object]]s, [[Loosely Coupled|Loosely coupled]], or [[Computer cluster|Tightly coupled]].

Distributed programming interrelates tightly with [[concurrent programming]] so much that they are sometimes not taught as distinct subjects [http://www.cs.technion.ac.il/~cs236370/main.html].