Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIRCast (FHIR)
-
2.1.0-ballot [deprecated]
-
Infrastructure & Messaging
-
STU
-
App launch scenarios and session discovery [deprecated]
-
-
Bas van den Heuvel / Trent Nolin: 7-0-0
-
Clarification
-
Non-substantive
Description
In a scenario in which the user manually starts two or more applications, the applications do not have the capability to establish a shared session topic. Since there's no "app launch", with its corresponding ability to exchange contextual information, the unique, unguessable, and session-specific hub.topic must be calculated by both the driving application's hub and the subscribing application. The synchronizing application could use a shared algorithm and secret to generate the hub.topic.
Why must the topic be unique and unguessable?
Especially in this case, a predictable value would be preferred.
Attachments
Issue Links
- is duplicated by
-
FHIR-37113 Add example with pre-aligned topic
- Duplicate
- is voted on by
-
BALLOT-35253 Negative - Bas van den Heuvel : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35860 Negative - Javier Espina : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36002 Negative - David Simons : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36098 Negative - Peter Kranich : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36169 Negative - Lisson Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36456 Negative - Chris Melo : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35789 Negative - Vadim Peretokin : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35931 Negative - Olivia Bellamou-Huet : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
- relates to
-
FHIR-37067 Unguessable topic needed?
- Applied