Right now, we only have a "delay" mechanism, but it does not help controlling the number of requests made to a server when used on an "update" behavior (i.e. action="replace").
We would like to introduce support for "throttle" and "debounce" mechanisms. The main use case will be to have more control over when a request is fired in reaction to a user interaction, i.e. changing the value of a text-field.
This mechanism should also work with the recently added "sync" attributes (see #1243).
Right now, we only have a "delay" mechanism, but it does not help controlling the number of requests made to a server when used on an "update" behavior (i.e.
action="replace").We would like to introduce support for "throttle" and "debounce" mechanisms. The main use case will be to have more control over when a request is fired in reaction to a user interaction, i.e. changing the value of a text-field.
This mechanism should also work with the recently added "sync" attributes (see #1243).