ALMAS 1.3 RTF Avatar
  1. OMG Issue

ALMAS13 — Coordination of unique request IDs

  • Key: ALMAS13-3
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The spec assumes "... that request IDs are generated by the caller and that they are unique across all ALMAS callers."
    This assumption imposes system implementation specific behaviour on users of the ALMAS specification and reduces portability across ALMAS systems.

  • Reported: ALMAS 1.1 — Tue, 8 Feb 2022 08:59 GMT
  • Disposition: Resolved — ALMAS 1.3
  • Disposition Summary:

    Request Uniqueness to be through Producer ID and Request ID

    ALMAS Producers (Clients) already specify a combination of request_id and producer_id in their method calls to ALMAS Manager. Therefore as producer_Id is unique to a producer request_id should only need to be unique to a single producer (client). This is advantageous as it does not require management to (for instance) pre-allocate request id ranges to different clients.
    A second consideration is that to apply the DDS Security model topic instance should be unique to a client so that each client is only permissioned for the data that relates to it. Therefore topic names should be post-fixed with the producer ID.

  • Updated: Fri, 30 Jun 2023 20:30 GMT