I’ve used the queuing approach, and it works well as you can defer that processing until your server load is idle, letting you manage your load quite effectively if you can partition off “tasks which aren’t urgent” easily. Rolling your own isn’t too tricky, here’s a few other options to check out: GearMan – this … Read more
Use Platform.runLater(…) for quick and simple operations and Task for complex and big operations . Use case for Platform.runLater(…) Use case for Task: Task Example in Ensemble App Example: Why Can’t we use Platform.runLater(…) for long calculations (Taken from below reference). Problem: Background thread which just counts from 0 to 1 million and update progress … Read more
You can’t. Tasks use background threads from the thread pool. Also canceling threads using the Abort method is not recommended. You may take a look at the following blog post which explains a proper way of canceling tasks using cancellation tokens. Here’s an example: class Program { static void Main() { var ts = new … Read more
Thread is a lower-level concept: if you’re directly starting a thread, you know it will be a separate thread, rather than executing on the thread pool etc. Task is more than just an abstraction of “where to run some code” though – it’s really just “the promise of a result in the future”. So as … Read more
Note the guidelines for performing work on a UI thread, collected on my blog: Don’t block the UI thread for more than 50ms at a time. You can schedule ~100 continuations on the UI thread per second; 1000 is too much. There are two techniques you should use: 1) Use ConfigureAwait(false) when you can. E.g., … Read more
Acquiring a value via an async method: var result = Task.Run(() => asyncGetValue()).Result; Syncronously calling an async method Task.Run( () => asyncMethod()).Wait(); No deadlock issues will occur due to the use of Task.Run.