What's needed?
Currently, the bounds provided by clients get invalidated after 5 seconds by default. The API could be extended to allow clients specify their own durations for this.
Proposed solution
No response
Use cases
At the moment, the default duration for bounds to stay valid is 5 seconds. Which means users need to keep sending bounds, otherwise they will lapse. Assuming a user needs to apply the same pair of bounds for the next 15 minutes, then they would need the same pair of bounds at least 180 times for it to be valid over the whole 15 minute window. Having the ability to provide custom validity durations will help reducing this overhead.
Alternatives and workarounds
No response
Additional context
No response
What's needed?
Currently, the bounds provided by clients get invalidated after 5 seconds by default. The API could be extended to allow clients specify their own durations for this.
Proposed solution
No response
Use cases
At the moment, the default duration for bounds to stay valid is 5 seconds. Which means users need to keep sending bounds, otherwise they will lapse. Assuming a user needs to apply the same pair of bounds for the next 15 minutes, then they would need the same pair of bounds at least 180 times for it to be valid over the whole 15 minute window. Having the ability to provide custom validity durations will help reducing this overhead.
Alternatives and workarounds
No response
Additional context
No response