Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8927

[fiware-stackoverflow] FIWARE - Orion and STH duplicated notifications

    Details

      Description

      Created question in FIWARE Q/A platform on 28-01-2017 at 21:01
      Please, ANSWER this question AT https://stackoverflow.com/questions/41914246/fiware-orion-and-sth-duplicated-notifications

      Question:
      FIWARE - Orion and STH duplicated notifications

      Description:
      I have a scenario where two or more subscriptions were made to some entity (with the same notification url). In this case, I have many of the same subscriptions. When the attributes related to subscriptions conditions are updated, I have as many notifications as subscriptions I made. This way, I have unnecessary messages, resulting in unnecessary processing.

      Is there a way to deal with this? Both Orion and STH Comet do not handle with this. Maybe Orion and STH can deny the creation of a subscription that already exists. If this Orion behavior is updated, maybe STH Comet does not need to handle that.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 15:12|CREATED monitor | # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 15:12|CREATED monitor | # answers= 1, accepted answer= True
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 18:08|UPDATED status: transition Answer| # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 18:08|UPDATED status: transition Answer| # answers= 1, accepted answer= True
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 21:08|UPDATED status: transition Finish| # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 21:08|UPDATED status: transition Finish| # answers= 1, accepted answer= True

          People

          • Assignee:
            backlogmanager Backlog Manager
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: