dido:99_annexes:annex-b-terms-and-definitions:r:responder_role

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:r:responder_role [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-b-terms-and-definitions:r:responder_role [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Responder Role ======
  
 +[[dido:99_annexes:annex-b-terms-and-definitions:r:start|Return to R Terms]]
 +
 +===== Discussion =====
 +
 +A Responder Role identifies a Logical Node's responsibility for receiving a request and producing a response or outcome.
 +
 +The Responder Role supports request/response interaction without prescribing a technology, protocol, or execution model. The Logical Architecture identifies the request, the response, the Logical Data Structure Definitions, the participating Logical Nodes, the Runtime Plane, and the traceability expectations.
 +
 +A Logical Node performing a Responder Role applies its assigned logical responsibility to the request and produces a response, decision, acknowledgement, result, or error outcome.
 +
 +===== Definition =====
 +
 +//Communication Role responsible for responding to a request.//
 +
 +===== Source =====
 +
 +Specialization of Communication Endpoint and Node Role from Part 1, Sections 7.6 and 7.4; generalised from request/response, control, policy, and service-interaction material in the original FX Demo Reference Architecture.
 +
 +===== Note =====
 +
 +A Responder Role does not require REST, RPC, blocking calls, or direct service invocation.
 +
 +===== Example =====
 +
 +A logical Policy Evaluation Node performs a Responder Role when it receives a release-evaluation request and returns a policy decision.
 +
 +----
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:r:start|Return to Top]]