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

FIWARE.Request.Tech.Data.OrionContextBroker.Orion Context Broker subscriptions question

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-TECH-HELP
        • Labels:
          None

          Description

          Hi,

          as I read, Orion CB will send a notification as soon as a new subscription
          is created, because (quoting) "Orion Context Broker considers the
          transition from "non existing subscription" to "subscribed" as a change."
          Is there a way to avoid first notification with ONCHANGE subscriptions,
          without having to manually check in code (eg: with a firstTime boolean)?
          As i'm developing an android app, i find it rather stupid that as soon as
          an user enables a rule, he gets spammed with an useless (at that time)
          notification.

          Thank you very much,
          Federico Di Pierro

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-incense-coaching@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-incense-coaching mailing list
          Fiware-incense-coaching@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-incense-coaching
          [Created via e-mail received from: Federico Di Pierro <f.dipierro@atooma.com>]

            Issue Links

            relates to

            extRequest - Request from external stakeholder received in the help desk HELC-1334 FIWARE.Request.Coach.INCENSe.Orion Context Broker subscriptions question

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              fermin Fermín Galán added a comment -

              The issue has been emailed:

              • Time sent: 05/Apr/16 6:55 PM
              • To: f.dipierro@atooma.com
              • with subject: *(HELP-6316) [Fiware-incense-coaching] Orion Context Broker subscriptions question *

              Dear Federico,

              Initial notification is synchronous to the subscription operation, thus is a way of getting the "initial state" of the context covered by the subscription before starting getting notifications. You could argue that a a syncronous query operation (e.g. GET /v2/entities, etc.) could be used to get the initial state at the same time of doing the subscription, but race conditions may occur beetween both operations so the initial notification is a more precise mechanism.

              Is this precise "initial state" useless? Well, it depends on the use case. The optimal solution would be to make this feature configurable and we have an open issue about that:

              https://github.com/telefonicaid/fiware-orion/issues/920

              Please add a +1 to that issue if you suppor the idea. Thanks!

              Best regards,

              ------
              Fermín

              Show
              fermin Fermín Galán added a comment - The issue has been emailed: Time sent: 05/Apr/16 6:55 PM To: f.dipierro@atooma.com with subject: *( HELP-6316 ) [Fiware-incense-coaching] Orion Context Broker subscriptions question * Dear Federico, Initial notification is synchronous to the subscription operation, thus is a way of getting the "initial state" of the context covered by the subscription before starting getting notifications. You could argue that a a syncronous query operation (e.g. GET /v2/entities, etc.) could be used to get the initial state at the same time of doing the subscription, but race conditions may occur beetween both operations so the initial notification is a more precise mechanism. Is this precise "initial state" useless? Well, it depends on the use case. The optimal solution would be to make this feature configurable and we have an open issue about that: https://github.com/telefonicaid/fiware-orion/issues/920 Please add a +1 to that issue if you suppor the idea. Thanks! Best regards, ------ Fermín
              Hide
              Permalink
              fw.ext.user FW External User added a comment -

              Thanks, voted.
              Making it configurable would be a huge step forward.

              Again, thank you very much.

              Federico Di Pierro

              Show
              fw.ext.user FW External User added a comment - Thanks, voted. Making it configurable would be a huge step forward. Again, thank you very much. Federico Di Pierro

                People

                • Assignee:
                  fermin Fermín Galán
                  Reporter:
                  fw.ext.user FW External User
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: