Group:
object-oriented programming
Topic:
actor machines
Topic:
attachments to electronic mail
Topic:
computational mail
Topic:
implementing distributed systems and applications
Topic:
mobile code
Topic:
multi-media and electronic mail
Topic:
object serialization
Topic:
parameter passing by message
Topic:
parameter passing by reference
Topic:
process migration
Topic:
shared objects
Topic:
structural equivalence vs. name equivalence of data types
| |
Summary
Objects have a user-defined type and typically point to other objects. Sending an object across a network can be difficult to achieve. Problems include reference parameters and type equivalence. The basic technique is to serialize the object with sufficient information to recreate that object at the other end.
Immutable objects simplify communication in a distributed system. (cbb 8/06)
Subtopic: serialization 
| Quote: serializing and deserializing arguments is expensive for remote method invocation (RMI) [»konoK4_2000]
| | Quote: direct serialization using the receiver's in-memory representation; dynamically generated by partial evaluation; 2-3x faster [»konoK4_2000]
|
Subtopic: sending object-oriented objects
| Quote: object-orientation includes moving arbitrary data types transparently across computing barriers
|
Subtopic: sending immutable objects
| Quote: ESP transmits deep copies of immutable objects by incrementing deep reference counts; keeps memory allocation local to a process [»kumaS6_2002]
| | Quote: Cosmos has immutable objects that are transformed into new objects by atomic actions [»walpJ6_1988]
| | Quote: use Guava values to pass complex data structures between monitors [»bacoDF10_2000]
|
Subtopic: sending forms
| Quote: a Piccola service consists of agents that send and receive forms via buffered channels
|
Subtopic: printing and editing as object transfers
| Quote: printing could be projecting an object across the memory-to-printer barrier, or editing across a memory-to-user barrier [»coxBJ7_1983]
|
Subtopic: problem of reference parameters
| Quote: reference parameters across processors either require expensive messages or access delays [»donnMD_1987, OK]
| | Quote: by requiring strong assignment (var<-val) for files, files can not use reference values [»demeA3_1979]
|
Subtopic: problem of name equivalence
| Quote: with name equivalence, a type only has meaning in a particular program; causes problems for distributed systems and persistent data; simple changes can undo pickled representations
|
Related Topics
Group: object-oriented programming (26 topics, 822 quotes)
Topic: actor machines (2 items)
Topic: attachments to electronic mail (4 items)
Topic: computational mail (11 items)
Topic: implementing distributed systems and applications (41 items)
Topic: mobile code (14 items)
Topic: multi-media and electronic mail (5 items)
Topic: object serialization (13 items)
Topic: parameter passing by message (31 items)
Topic: parameter passing by reference (11 items)
Topic: process migration (3 items)
Topic: shared objects (13 items)
Topic: structural equivalence vs. name equivalence of data types
(30 items)
|
