The CopperLan framework offers several messaging solutions. An application can declare outgoing or incoming Endpoints, establish connections, send & receive Application Messages. This is the standard messaging, performed between an Output and a set of connected Inputs. Automation flags, time-stamping, recording destinations handling and a transaction mechanism are also available for the application developer.

A short messaging format is also available, based on Signals. These messages can be sent directly to a device, or broadcast on the network without support of Output or Input.

CopperLan messaging supports single destination, multicast, and broadcast; these are managed automatically by the system. For completeness, we should mention System messages as well as mechanisms for flow control and message priority that are not under direct control of the developer.

Note: Endpoints are defined by their CopperLan identity, which is independent of their physical location. If a connection is pointing to a specific Endpoint, it can be restored later even if this Endpoint changed from physical location (going from machine A to machine B) or physical transport used (e.g. from USB to Ethernet).

Additional information