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
Sort-of related to #65 (but for usage-based resource consumption instead of idle).
Currently, if no traffic has been received for a session in at least 6 seconds, then the next time we send a packet we also start a search. This is to quickly detect if a session has dropped due to coord changes.
What we should do is switch to sending sessionPings (throttled to a max of 1/second/session). If an additional T time (3-6 seconds?) passes without receiving a sessionPong, then try a search instead. Most of the time, a lack of traffic probably just means the session was idle, so a search is overkill.
The text was updated successfully, but these errors were encountered:
Sort-of related to #65 (but for usage-based resource consumption instead of idle).
Currently, if no traffic has been received for a session in at least 6 seconds, then the next time we send a packet we also start a search. This is to quickly detect if a session has dropped due to coord changes.
What we should do is switch to sending sessionPings (throttled to a max of 1/second/session). If an additional T time (3-6 seconds?) passes without receiving a sessionPong, then try a search instead. Most of the time, a lack of traffic probably just means the session was idle, so a search is overkill.
The text was updated successfully, but these errors were encountered: