Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-25823

hub.events field also required for websockets?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - No Change (View Workflow)
    • Priority: Highest
    • Resolution: Not Persuasive
    • Specification:
      FHIRCast (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Imaging Integration
    • Related URL:
    • Related Page(s):
      (NA)
    • Related Section(s):
      Subscription Request
    • Grouping:
    • Resolution Description:
      Hide

      hub.events are required also for websockets. There is no intention to use hub.events (or lack thereof) as an indication to close a websocket.

      Show
      hub.events are required also for websockets. There is no intention to use hub.events (or lack thereof) as an indication to close a websocket.
    • Resolution Vote:
      Isaac Vetter/Eric Martin: 16-0-2

      Description

      Are hub.events field also required for websockets? Typically, a new websocket end-point would be created for each subscription. Absence indicates, close websocket url.

        Attachments

          Issue Links

          is voted on by

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-11348 Affirmative - Bas van den Heuvel : 2020-Feb-FHIRCast R1 STU

          • Balloted

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bvdh Bas van den Heuvel
              Request in-person:
              Bas van den Heuvel
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: