Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
(NA)
-
-
Bas van den Heuval / Alex Z Liu: 7-0-0
-
Correction
-
Compatible, substantive
-
current
Description
Current language:
Following an accepted context change request, the Hub MAY re-use this value in the broadcasted event notifications.
(From https://chat.fhir.org/#narrow/stream/179271-FHIRcast/topic/Tracking.20events.20through.20acceptance)
If a Hub elects to assign a new ID to an app-supplied event when broadcasting it out, how can an app determine that the new event it sees is the same event it submitted?
> Bas van den Heuvel: not that I am aware off, and that will cause issues, especially in multi-tab applications (race condition that will start an endless loop of tab switches).
The possibility of an endless loop is bad! Perhaps we could say:
"Following an accepted context change request, the Hub MAY re-use this value in the broadcasted event notifications. If the Hub does not re-use the app-supplied value, it SHALL populate an "originalId" property with the app-supplied value".