Termination Reason MAX_EVENTS

[daniel-dierich]

Problem description
Hi all,

currently there is a Termination Reason MAX_EVENTS_REACHED defined. I know this max event logic from the other APIs. However there is no option to define this value. For example in Device Location geofencing subscriptions you can define the value using "subscriptionMaxEvents": 5 in your request.

Expected behavior
I would propose to add the request parameter.

Alternative solution
Alternatively the Termination Reason could be removed.

[gregory1g]

as far as I remember, we did not found a use case for subscripting to a fixed number of simswap events.
At the same time the implementation would require a state (the counter) to be kept (this would impact horizontal scalability of the service). Therefore the decision was - do no support even counter based subscription, while termination reason was kept to keep alignment with the general commonalities design.

[daniel-dierich]

I understand. Thank you for explaining!

[bigludo7]

@gregory1g @daniel-dierich I convert this issue in discussion as it did not required code change.