Skip to content

Commit

Permalink
Update documentation/API-design-guidelines.md
Browse files Browse the repository at this point in the history
Co-authored-by: Pedro Díez García <pedro.diezgarcia@telefonica.com>
  • Loading branch information
bigludo7 and PedroDiez authored Feb 13, 2024
1 parent 188cd6d commit 4d7ff14
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion documentation/API-design-guidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -1352,7 +1352,7 @@ Following Error code must be present:
* case3: subscriber requests the `DELETE` operation for the subscription (if the subscription did not have a subscriptionExpireTime or before subscriptionExpireTime expires).
* case4: subscription ends on operator request.
It could be useful to provide a mechanism to inform subscriber for all case. In this case, a specific event type could be used.
It could be useful to provide a mechanism to inform subscriber for all cases. In this case, a specific event type could be used.
_Termination rules regarding subscriptionExpireTime & subscriptionMaxEvents usage_
* When client side providing a `subscriptionExpireTime` and/or `subscriptionMaxEvents` service side has to terminate the subscription without expecting a `DELETE` operation.
Expand Down

0 comments on commit 4d7ff14

Please sign in to comment.