Text only applies to webhooks – how does this work for websockets?

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Subscription Request
    • Hide

      >Text only applies to webhooks – how does this work for websockets? Easiest – each subscribe creates its own wss url. Unsubscribe to url closes it. A change in subscriptions would then be: subscribe to new set, close old one.

       

      Yes, agree. The simplest/best approach is for the subscriber to open a new subscription and close the old one when they wish to change the subscription.

      Show
      >Text only applies to webhooks – how does this work for websockets? Easiest – each subscribe creates its own wss url. Unsubscribe to url closes it. A change in subscriptions would then be: subscribe to new set, close old one.   Yes, agree. The simplest/best approach is for the subscriber to open a new subscription and close the old one when they wish to change the subscription.

      Text only applies to webhooks – how does this work for websockets? Easiest – each subscribe creates its own wss url. Unsubscribe to url closes it. A change in subscriptions would then be: subscribe to new set, close old one.

      Existing Wording:

      Hubs SHALL allow subscribers to re-request subscriptions that are already activated. Each subsequent and verified request to a Hub to subscribe or unsubscribe SHALL override the previous subscription state for a specific hub.topic, hub.callback / hub.channel.endpoint url, and hub.events combination. For example, a subscriber MAY modify its subscription by subscribing to or unsubscribing from additional events by sending subscription requests for additional events with the same topic and callback/endpoint url.

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: