A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/dotnet/reactive/issues/1270 below:

Could we have Throttle by task? · Issue #1270 · dotnet/reactive · GitHub

Feature request

I don't know if this operator could be fabricated from other function. But I want a function that could be Throttle the input from stream while the current handler wasn't finished, but not throttle by timing

Suppose there is a http post function that listen to UI input change and send that data to server

ISubject<string> nameTextField;
nameTextField.Throttle(async(newName) => {
    await HTTPPost(newName);
    return newName;
}).Subscribe((newName) => {
    Console.WriteLine("Updated name to : " + newName);
});

What I would like it to happen is, this function would act like Select but it would buffer data stream to emit only one last output at a time
1 - If the data was sent to this function for the first time, it will trigger the function immediately
2 - If data was sent to this function, but the previous execution still not finished. Then it would kept that data and wait until the previous execution finished then trigger the function again
3 - If yet another data was sent, it would dispose the previous cache and kept the new one in the waiting queue instead

So as the example. If there is any changed from user input, it will send HTTP Post to server immediately. But if there was internet lagging while user was changing that text field multiple time. I don't want HttpPost to be called parallel, but if the previous one finished I would like to Post the latest value that user have changed

Could we have this kind of function or there was a way to do this already?


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4