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 Feb 1, 2023. It is now read-only.
Currently we debounce sending wants by a millisecond. If a client sends continuous requests at a higher frequency than the debounce time, the request will never be sent.
Proposed Solution:
Add a debounce function to the message queue that takes two parameters:
debounce time
wait at least this interval after the last invocation before calling the target function
max time
if we're still debouncing after this amount of time, don't wait any more, call the target function anyway
The text was updated successfully, but these errors were encountered:
This:
* Makes it easy to send immediately if we wait too long and/or if we have enough
to send.
* Is significantly more efficient than the debounce library as it doesn't spin
off a bunch of "after" timers.
fixes#245
Currently we debounce sending wants by a millisecond. If a client sends continuous requests at a higher frequency than the debounce time, the request will never be sent.
Proposed Solution:
Add a debounce function to the message queue that takes two parameters:
wait at least this interval after the last invocation before calling the target function
if we're still debouncing after this amount of time, don't wait any more, call the target function anyway
The text was updated successfully, but these errors were encountered: