Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:99_annexes:annex-b-terms-and-definitions:f:fx_control_command_endpoint [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:f:fx_control_command_endpoint [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== FX Control Command Endpoint ======
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +The FX Control Command Endpoint carries operational commands and command acknowledgements among FX logical Nodes.
 +
 +The endpoint supports operational coordination, status requests, pausing, resuming, retrying, recovery, initiating replay, configuration reload, and command acknowledgement. It carries FX Control Command and FX Command Acknowledgement information.
 +
 +The FX Control Command Endpoint participates primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]]. It also relates to the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] when command records and acknowledgement records support review, reconstruction, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]].
 +
 +===== Definition =====
 +
 +//[[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] carrying operational commands and command acknowledgements among FX logical Nodes//
 +
 +===== Source =====
 +
 +Specialization of Logical Communication Endpoint from [[fxdemo:02-part:start]], Section 7.2, Logical Command from [[fxdemo:02-part:start]], Section 8.6, Logical Acknowledgement from [[fxdemo:02-part:start]], Section 8.7, and [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] from [[fxdemo:01-part:start]], Section 8.2; generalised from control-plane command and acknowledgement material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
 +
 +===== Note =====
 +
 +The FX Control Command Endpoint does not prescribe a command protocol, orchestration command, API style, DDS Topic, REST resource, RPC method, queue, or deployment mechanism.
 +
 +===== Example =====
 +
 +The FX Registry and Coordination Node sends a retry command through the FX Control Command Endpoint, and the FX Validation Node returns an FX Command Acknowledgement.