You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the synchronous API client will poll asynchronous requests every 0.5s. This makes hitting the API rate limit quite likely once you introduce concurrency.
For the API client to not feel sluggish, the poll intervall likely shouldn't simply be increased to a few seconds. It could be dynamically increased to a max and/or be request type-dependent.
The text was updated successfully, but these errors were encountered:
Is there a way to implement web sockets in the back-end? This would make polling unnecessary. And feel much more native. The client would then just subscribe to the request_uuid and if something changes in the back-end the client is notified.
Currently the synchronous API client will poll asynchronous requests every 0.5s. This makes hitting the API rate limit quite likely once you introduce concurrency.
For the API client to not feel sluggish, the poll intervall likely shouldn't simply be increased to a few seconds. It could be dynamically increased to a max and/or be request type-dependent.
The text was updated successfully, but these errors were encountered: