Clarify the use of WebHooks vs. WebSockets

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Overview
    • Hide

      Except for over-the-wire content (e.g. the value of `hub.channel.type`), update the spelling/capitalization of the terms websocket and webhook to WebSocket and webhook. 

      We will not (yet?) add a recommendation ascribing hub.channel.types to pre-defined application architectures. 

      Show
      Except for over-the-wire content (e.g. the value of `hub.channel.type`), update the spelling/capitalization of the terms websocket and webhook to WebSocket and webhook.  We will not (yet?) add a recommendation ascribing hub.channel.types to pre-defined application architectures. 
    • Eric Martin / Bill Wallace: 8-0-0
    • Correction
    • Non-substantive

      FHIRcast enables a subscriber to receive notifications either through a WebHooks or over a WebSocket connection, and is modeled on the W3C WebSub RFC, such as its use of GET vs POST interactions and a Hub for managing subscriptions.
      However, this specification recommends WebSocket connections for browser-based communication and WebHooks for server-to-server communication. Implementers will select the communication protocol that appropriate for teach participating application

      Existing Wording:

      FHIRcast enables a subscriber to receive notifications either through a webhook or over a websocket connection, and is modeled on the W3C WebSub RFC, such as its use of GET vs POST interactions and a Hub for managing subscriptions

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: