Communication Role [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Communication Role ======

[[dido:99_annexes:annex-b-terms-and-definitions:c:start|Return to C Terms]]

===== Discussion =====

A Communication Role identifies how a Logical Node participates in a Logical Communication Endpoint.

Communication Roles describe logical participation in an exchange. They do not prescribe communication technology, protocol, deployment topology, or runtime packaging.

A Logical Node performs one or more Communication Roles for a given endpoint. The same Logical Node also performs different Communication Roles across different endpoints. For example, a Logical Node publishes health status, subscribes to configuration updates, consumes commands, and produces acknowledgements.

===== Definition =====

//Logical participation responsibility performed by a Logical Node at a Logical Communication Endpoint.//

===== Source =====

Specialization of Node Role and Communication Endpoint from Part 1, Sections 7.4 and 7.6; generalised from publisher, subscriber, command, control-plane, and topic-participation material in the original FX Demo Reference Architecture.

===== Note =====

A Communication Role belongs to the logical interaction model. It does not identify a deployed process, network connection, protocol binding, or middleware participant.

===== Example =====

A Logical Node performs a Publisher Role when it produces health-status information for a logical health-status endpoint.

----

[[dido:99_annexes:annex-b-terms-and-definitions:c:start|Return to Top]]