You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: