Knockout 3.3.0 rateLimit extender: choosing between per‑change timer reset and silent‑period reset

Goal

Apply the Knockout rateLimit extender to an observable bound to a UI input so that rapid user actions generate at most one notification per interval, thereby preventing alert noise while still delivering the final value after a burst of changes.

Uncertainty

The extender’s internal timer can be implemented either to reset on every new observable change or to wait for a period of silence before restarting. This design choice influences how bursty interactions are throttled and whether intermediate values are suppressed, but the documentation does not specify which behavior is guaranteed.

Should the rateLimit extender reset its timeout on each change, or only after a silent period? How does each approach affect the number of notifications during rapid bursts? What impact does the choice have on UI responsiveness and data consistency?