Stream: subscriptions
Topic: Required to support subscription.end and subscription.error?
Ellen Haglund (Feb 10 2022 at 10:06):
We have created a subscription service, but find it somewhat difficult to determine which parts are required (or shall-demands) and which parts we can omit for the time being. Is it a requirement to include support for subscription.end and subscription.error?
Gino Canessa (Feb 10 2022 at 15:30):
Since it is not mandatory, Subscription.end could either be supported or not. That said, it is good practice for your service to indicate that and respond appropriately. One option, documented in http#create) is to return an HTTP 422 with an OperationOutcome describing that end is not supported, in case clients are leaning on that functionality for something. There are likely other ways to go about this.
Since Subscription.error is server populated, there should not be anything you need to do there. I will also note that the element has been removed in R5 (in favor of using the SubscriptionStatus resource).
Last updated: Apr 12 2022 at 19:14 UTC
