Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIRCast (FHIR)
-
2.1.0-ballot [deprecated]
-
Infrastructure & Messaging
-
FHIRcast Observation
-
Event notification [deprecated]
-
2.5
-
-
Catie Ladd / Nick Radov : 5-0-1
-
Clarification
-
Non-substantive
Description
When should the Hub start ignoring that a web socket was closed? Immediately (i.e. return no error to the user)? Or return an error once to the user, and remove the subscription immediately at that moment? Or should the error be returned for every context change? But when does it stop? At some moment we can expect the user to know that something went wrong. So my suggestion would be to discard closed WebSocket connections after displaying an error to the user once that an app is no longer reachable (and didn’t unsubscribe).
Attachments
Issue Links
- relates to
-
FHIR-37083 Implementer feedback on syncerror
- Applied
- mentioned in
-
Page Loading...