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
{{ message }}
This repository has been archived by the owner on Mar 18, 2021. It is now read-only.
Since the server is asynchronous, there's currently not really a way to tell if it's "busy" (it's always possible to make more requests) but I think it would make sense to limit each client to one request at a time, since each new request means that we no longer care about the previous one anyway. This would require us to keep track of a client "session".
One way for the client to tell if the server is responding at all would be to do some form of "heartbeat" requests regularly, e.g. a HEAD request every ten seconds.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Notify the user about the status of the server: 'BUSY', 'PROCESSING_REQUEST', 'DOWN'...
The text was updated successfully, but these errors were encountered: