Stream: implementers
Topic: subscriptions and web sockets
Jens Villadsen (Sep 04 2017 at 07:56):
Section 2.47.6.2 - Server sends a "ping :id" message to notify the client each time a new result is available - why would the server not send the actual data instead? It saves round tripping.
Lloyd McKenzie (Sep 04 2017 at 15:34):
It's architecturally simpler if access control, privacy rules, etc. can all be triggered off of a query. As well, responses could potentially be large, so giving the client control over if/when/how to retrieve is helpful.
Grahame Grieve (Sep 05 2017 at 01:28):
it's up the subscription whether it asks for content, or just a ping/
Grahame Grieve (Sep 05 2017 at 01:28):
and up to the server whether it accepts or not
Jens Villadsen (Sep 05 2017 at 10:07):
right ... found it. thx
Jens Villadsen (Sep 05 2017 at 10:09):
@Lloyd McKenzie - i get there can be some security and control issues. I think there are at least to different use cases here ... using it within a closed ecosystem ('verified'applications) and an open eco system (3. party) where perhaps more security is needed
Grahame Grieve (Sep 05 2017 at 11:06):
indeed - which is why it can be with out without content
Patrick Werner (Feb 18 2019 at 16:01):
it's up the subscription whether it asks for content, or just a ping/
and up to the server whether it accepts or not
with websockets i only can use PING:
from: https://www.hl7.org/fhir/subscription.html#scope:
websocket: A PING message is sent to the designated URI i can't see the option for sending content through the websocket. The FHIR Structure of Subscription would allow this, but the text in 2.46.1 says otherwise.
Grahame Grieve (Feb 19 2019 at 01:06):
hmm I think my implementation allows it, but agree it's not in the spec
Patrick Werner (May 29 2019 at 22:41):
Last updated: Apr 12 2022 at 19:14 UTC
