Async/Await vs Threads

by

can it completely replace the old way of using Threads ?

No. A thread can do many more useful things. Await is specifically designed to deal with something taking time, most typically an I/O request. Which traditionally was done with a callback when the I/O request was complete. Writing code that relies on these callbacks is quite difficult, await greatly simplifies it.

capable of doing what ever a Thread can do asynchronously ?

Roughly. Await just takes care of dealing with the delay, it doesn’t otherwise do anything that a thread does. The await expression, what’s at the right of the await keyword, is what gets the job done. Ideally it doesn’t use a thread at all, it posts a driver request and once the driver completes the data transfer it generates a completion notification callback. Networking is by far the most common usage, latencies of hundreds of milliseconds are common and an inevitable side-effect of services moving from the desktop or a LAN into “the cloud”. Using such services synchronously would make a UI quite unresponsive.

only can be used with some methods like WebClient.DownloadStringAsync

No. You can use it with any method that returns a Task. The XxxxAsync() methods are just precooked ones in the .NET framework for common operations that take time. Like downloading data from a web server.

More Related Contents:

  1. If async-await doesn’t create any additional threads, then how does it make applications responsive?
  2. Run async method regularly with specified interval
  3. Cancelling a pending task synchronously on the UI thread
  4. ConfigureAwait pushes the continuation to a pool thread
  5. EF Data Context – Async/Await & Multithreading
  6. How to get awaitable Thread.Sleep?
  7. Queue of async tasks with throttling which supports muti-threading
  8. Async thread body loop, It just works, but how?
  9. The lack of non-capturing Task.Yield forces me to use Task.Run, why follow that?
  10. Async and Await with For Loop [duplicate]
  11. Wrapping ManualResetEvent as awaitable task
  12. Attempted to read or write protected memory. This is often an indication that other memory is corrupt
  13. Why should I prefer single ‘await Task.WhenAll’ over multiple awaits?
  14. Is it considered acceptable to not call Dispose() on a TPL Task object?
  15. Re-entrant locks in C#
  16. Synchronously waiting for an async operation, and why does Wait() freeze the program here
  17. Getting the thread ID from a thread
  18. What does SynchronizationContext do?
  19. Is there a way to indefinitely pause a thread?
  20. How to run a Task on a custom TaskScheduler using await?
  21. Pattern for calling WCF service using async/await
  22. Monitor vs lock
  23. Await operator can only be used within an Async method [duplicate]
  24. Proper way to Dispose of a BackGroundWorker
  25. Why am I getting this error:”Cross-thread operation not valid: Control lbFolders accessed from a thread other than the thread it was created on.”?
  26. Can you link to a good example of using BackgroundWorker without placing it on a form as a component?
  27. Should thread-safe class have a memory barrier at the end of its constructor?
  28. Faulted vs Canceled task status after CancellationToken.ThrowIfCancellationRequested
  29. When is the best place to use Task.Result instead of awaiting Task
  30. Calling an async method from a synchronous method

Leave a Comment