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, if there aren't any new events at the beginning of a long-polled /sync call, we just wait for the timeout (capped to 30s) before returning an empty response. The implementation for this behavior is here. What we should be doing instead is watching for new events while we wait for the timeout, and returning a response with new events immediately if any occur. I suspect that fixing this will be a noticeable improvement in message delivery latency for most clients.
The text was updated successfully, but these errors were encountered:
Currently, if there aren't any new events at the beginning of a long-polled
/sync
call, we just wait for the timeout (capped to 30s) before returning an empty response. The implementation for this behavior is here. What we should be doing instead is watching for new events while we wait for the timeout, and returning a response with new events immediately if any occur. I suspect that fixing this will be a noticeable improvement in message delivery latency for most clients.The text was updated successfully, but these errors were encountered: