Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 3 Fundamentals : Messages and Data

Messages and Data
Computer hardware and operating system platforms use different conventions for data representation. Data from one platform can be unintelligible on another platform. Rendezvous software uses a unified data representation to exchange messages among all supported platforms.
Messages are the common currency that Rendezvous programs use to exchange data. Rendezvous messages contain fields of self-describing data. Every message has a subject name, which describes its destination.
All data that enters or leaves a program through the Rendezvous daemon must be encapsulated in the fields of a message. As an abstraction, a message is a collection of self-describing data fields, which travel together between programs, processes or threads.
Programs can manipulate messages even before opening the Rendezvous environment (see The Rendezvous Environment).
Fields
Each field contains one data item of a specific datatype. Programs can identify and access the individual fields of a message either by name or by numeric identifiers.
From the programmer’s point of view, a message is a set of fields. Programs manipulate messages using API calls. A program can create a message, add fields to it, remove fields from it, get a field from a message, update the data value in a field, and destroy a message.
Wire Format
At a lower level, beyond these abstract operations, each message exists as a byte sequence in Rendezvous wire format—a uniform representation suitable for network communication among diverse hardware, operating system, and programming language platforms. Programs never access this representation, yet it is the foundation for all Rendezvous communication.
See Also
Data.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved