Basically a UI optimization. Instead of firing multiple requests to the server a lot, we know that a specific UI event may happen multiple times in a short peri

Basically a UI optimization. Instead of firing multiple requests to the server a lot, we know that a specific UI event may happen multiple times in a short period, so we "throttle" it by only performing the request once at a time and only re-requesting it if it was requested again. So far it's always been a UI optimization like that. You could handle this at the connection layer, but I liked how it integrates with actions better (it gives a finer control over when actions are dispatched)