-
Notifications
You must be signed in to change notification settings - Fork 22
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
Comments
In what scenario would more than one client be sharing the same callback? |
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. |
Ahhh. That makes sense. I'll need to check my him implementation to make
sure that works
…On Sun, Sep 15, 2019, 10:43 AM Will Maethner ***@***.***> wrote:
Hey @gkustas <https://github.com/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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#287?email_source=notifications&email_token=ABODZ3VEM7LSFMNUNFAE4N3QJZCY5A5CNFSM4IWXHRD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XSE4Q#issuecomment-531571314>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABODZ3WIYGRFUKJOFJGZIJTQJZCY5ANCNFSM4IWXHRDQ>
.
|
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,
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).
The text was updated successfully, but these errors were encountered: