ALMAS 1.0 FTF Avatar
  1. OMG Issue

ALMAS — mapping a number of methods

  • Key: ALMAS-30
  • Legacy Issue Number: 13022
  • Status: closed  
  • Source: Anonymous
  • Summary:

    It would be better to map a number of methods, which are now directly mapped on DDS level constructs, on control topics because of two reasons: 1. Without control topics a producer can not be directly notified of a producer or system related error/problem. E.g. when a producer produces a new alert, he can not be notified that this was not succesfull because no active receivers are present. 2. Much more important: An alert contains ""static"" information but also state information (e.g. AlertId, Currentstate, Receivers etc.). Only ALMAS should be allowed to maintain this information, not a producer. Because a producer can now write a complete Alert, it may also write state information. This would violate data hiding principles and therefore ALMAS would be unnecessarely complex and obscure. Solution: The following methods should map on control topics: 1. UpdateDynamicMessageData 2. SetAlertInhibited 3. RemoveAlertsWithDynamicMessageData 4. RaiseAlertFromOverrides 5. RaiseAlertFromData 6. UpdateAlert

  • Reported: ALMAS 1.0b1 — Fri, 31 Oct 2008 04:00 GMT
  • Disposition: Resolved — ALMAS 1.0
  • Disposition Summary:

    Remove the following items from table in section 9.3.2:
    ALMAS Manager - UpdateDynamicMessageData
    ALMAS Manager - SetAlertInhibited
    ALMAS Manager - RemoveAlertsWithDynamicMessageData
    ALMAS Producer - RaiseAlertFromOverrides
    ALMAS Producer - RaiseAlertFromData
    ALMAS Producer - CancelAlert

    Add the following new topics ALMAS_UpdateDynamicMessageData,
    ALMAS_SetAlertInhibited, ALMAS_RemoveAlertsWithDynamicMessageData , ALMAS_RaiseAlertFromOverrides,
    to DCPS IDL
    For the purpose of these new topics, note that attributes are removed from struct ALMAS_AlertDataType and now contained in new struct ALMAS_AlertDataAttributesType.

  • Updated: Fri, 6 Mar 2015 20:57 GMT