Portable Distributed Objects

related topics
{system, computer, user}
{math, number, function}
{work, book, publish}
{rate, high, increase}
{game, team, player}

Portable Distributed Objects, or PDO, is a programming API for creating object-oriented code that can be executed remotely on a network of computers. It was created by NeXT Computer, Inc. using their OpenStep system, whose use of Objective-C made the package very easy to write. It was characterized by its very light weight and high speed in comparison to similar systems such as CORBA.

Versions of PDO were available for Solaris, HP-UX and all versions of the OPENSTEP system. A version that worked with Microsoft OLE was also available called D'OLE,[1] allowing distributed code written using PDO on any platform to be presented on Microsoft systems as if they were local OLE objects.

PDO was one of a number of distributed object systems created in the early 1990s, a design model where "front end" applications on GUI-based microcomputers would call code running on mainframe and minicomputers for their processing and data storage. Microsoft was evolving OLE into the Component Object Model (COM) and a similar distributed version called DCOM,[citation needed] IBM had their System Object Model (SOM/DSOM), Sun Microsystems was promoting their Distributed Objects Everywhere, and there were a host of smaller players as well. With the exception of the limited functionality in COM,[citation needed] most of these systems were extremely heavyweight, tended to be very large and slow, and often were very difficult to use.

PDO, on the other hand, relied on a small number of features in the Objective C runtime to handle both portability as well as distribution. The key feature was the language's support for a "second chance" method in all classes; if a method call on an object failed because the object didn't support it (normally not allowed in most languages due to strong typing), the runtime would then bundle the message into a compact format and pass it back into the object's forwardInvocation method.

The normal behavior for forwardInvocation was to return an error, including details taken from the message (the "invocation").[clarification needed] PDO instead supplied a number of new objects with forwardInvocation methods that passed the invocation object to another machine on the network, with various versions to support different networks and platforms. Calling methods on remote objects was almost invisible; after some network setup (a few lines typically) PDO objects were instantiated locally and called the same way as any other object on the system. The PDO object then forwarded the invocation to the remote computer for processing and unbundled the results when they were returned.

Full article ▸

related documents
Adapter pattern
Maclisp
Creator code
Run-length encoding
Triple DES
Synchronized Multimedia Integration Language
Wikipedia:Free On-line Dictionary of Computing/I - K
RenderMan Interface Specification
AutoLISP
Monolithic kernel
Debugger
Bourne shell
IBM 1620 Model I
386BSD
Server-side scripting
ScriptBasic
XPCOM
Command-line interpreter
Program counter
Time to live
BASIC09
Linker
Z3 (computer)
Randomizer
Information hiding
CHS conversion
Pseudonymous remailer
Remote procedure call
Document Object Model
Analytical engine