Feature idea that came up will discussing slow synchronous processing requests:
Let the user (optionally) define a maximum time to spend on a synchronous /result request:
e.g. "if this takes more than 20 seconds, you can just abort this, I won't be looking at the result probably"
Example use case: interactive viewer, where user is relatively quickly panning and zooming around.
Backend can then free computing resources more efficiently.
And ideally, if backend can reasonably predict how long a particular request will take, it can even avoid burning resources that would be wasted.
Feature idea that came up will discussing slow synchronous processing requests:
Let the user (optionally) define a maximum time to spend on a synchronous
/resultrequest:e.g. "if this takes more than 20 seconds, you can just abort this, I won't be looking at the result probably"
Example use case: interactive viewer, where user is relatively quickly panning and zooming around.
Backend can then free computing resources more efficiently.
And ideally, if backend can reasonably predict how long a particular request will take, it can even avoid burning resources that would be wasted.