Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating a subscription -- clarify how this works. #287

Open
isaacvetter opened this issue Sep 14, 2019 · 3 comments
Open

Updating a subscription -- clarify how this works. #287

isaacvetter opened this issue Sep 14, 2019 · 3 comments

Comments

@isaacvetter
Copy link
Collaborator

During the HL7 Sept FHIRcast connectathon track, @wmaethner , Bas, and I talked through -

When creating a new subscription for the same topic and callback url as an existing subscription,

  • is the client required to unsibscribe from the initial subscription? No
  • is the hub responsible for notifying client of ending of first subscription? No

Need to clarify that the Hub responds as part of the intent verification with the events that a subscriber is successfully using.

For websockets new subscriptions for the same topic should be on new websocket connections (we think).

@gkustas
Copy link

gkustas commented Sep 15, 2019

In what scenario would more than one client be sharing the same callback?

@wmaethner
Copy link
Collaborator

Hey @gkustas, multiple clients shouldn't have the same callback, it should be unique. The situation we were thinking of was where the client makes a subscription, but then later wants to add or change the events it is subscribed to (e.g. they subscribe to patient events, then later want to also subscribe to study events). In that case it will be the same topic and callback.

@gkustas
Copy link

gkustas commented Sep 15, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants