Stream: fhircast-github
Topic: fhircast-docs / Issue #87 How to identify WebSocket subsc...
Github Notifications (FHIRcast) (Mar 25 2019 at 14:27):
gkustas opened Issue #87
Up until now, I have been using a hack to unsubscribe my websocket client from the hub: I simply close the websocket, which triggers the hub to remove the websocket from it's collection of connections, and remove the subscription that is referenced by that connection item.
This shouldn't be a permanent solution. There needs to be a unique identifier (as the hub.callback is required to be, and is used by the current RESTful sandbox implementations).
Should we use the hub.callback and create a unique url for identification purposes? It could be generated using the client's IP address and port in order to keep it unique?
Last updated: Apr 12 2022 at 19:14 UTC
