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

February 2020 Ballot: Optionality of Hub Support of hub.channel.type #305

Open
EricOnFHIR opened this issue Dec 16, 2019 · 0 comments
Open

Comments

@EricOnFHIR
Copy link
Collaborator

Should FHIRcast Hubs be able to support only a single channel type or is it mandatory that they support both webhook and websocket?

Assuming support for one or the other channel type being optional, should we explicitly mention in 'Subscription Response' section that one reason for denying a subscription request is that the Hub does not support the requested hub.channel.type? For example, add the quoted and italicized text:

was received and will now be verified by the Hub. "Since support of both Hub channel types is not required the Hub may reject the subscription request if the requested hub.channel.type is not supported." If using websockets

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

1 participant