Are you there, asynchronously written value?

by

In the above example, it is safe to read the m_GetResponse because assignment will happen in same UI thread given that this is being called from UI.

This is because SynchronizationContext will be captured and continued when the async method resumes. So it is the same UI thread which writes the field and reading it. This isn’t a problem here. Refer my related answer here

If called from non UI context, there is no guarantee that continuations will be ran in same thread. Usually it will be ran in ThreadPool thread. Given that the field read isn’t volatile it is possible that you could get the previous value if necessary barriers are not inserted. But you don’t need to worry about it because TPL already does this for you.

From the above link

Yes, TPL includes the appropriate barriers when tasks are queued and
at the beginning/end of task execution so that values are
appropriately made visible

So with TPL, you don’t need to worry about memory barriers given that the Tasks are already completed. But if you’re creating threads manually(which you shouldn’t be doing) and dealing with threads directly –you’ll have to insert necessary memory barriers.

Btw, ReadToEnd is a blocking call. I would not call it in UI thread. I’d use ReadToEndAsync instead to make your UI thread free. And I’ll not use field here; I’ll return the value from async method because every method call is just dependent on the parameter so it makes sense to return the value from the method.

So, your method will become something like the following

private async Task<string> SendDataAsync(string url)
{
    var request = WebRequest.Create(url);
    using(var response = await request.GetResponseAsync());
    using(var reader = new StreamReader(request.GetResponseStream());
        return await reader.ReadToEndAsync();
}

More Related Contents:

  1. Is it ok to await the same task from multiple threads – is await thread safe?
  2. How and when to use ‘async’ and ‘await’
  3. How would I run an async Task method synchronously?
  4. Should I avoid ‘async void’ event handlers?
  5. await Task.Run vs await
  6. How do yield and await implement flow of control in .NET?
  7. Fire and forget async method in asp.net mvc
  8. Why File.ReadAllLinesAsync() blocks the UI thread?
  9. How can I call an async method in Main?
  10. Enforce an async method to be called once
  11. How to protect resources that may be used in a multi-threaded or async environment?
  12. Why use Async/await all the way down
  13. Using async without await
  14. async/await different thread ID
  15. awaitable Task based queue
  16. Different forms of the WCF service contract interface
  17. Named Mutex with await
  18. Is async HttpClient from .Net 4.5 a bad choice for intensive load applications?
  19. How does async works in C#?
  20. How could the new async feature in c# 5.0 be implemented with call/cc?
  21. What is the correct way to cancel an async operation that doesn’t accept a CancellationToken?
  22. Async ShowDialog
  23. Async thread body loop, It just works, but how?
  24. Horrible performance using SqlCommand Async methods with large data
  25. How to throttle multiple asynchronous tasks?
  26. Await vs Task.Result in an Async Method [duplicate]
  27. call async method without await #2
  28. Async and Await with For Loop [duplicate]
  29. When is the best place to use Task.Result instead of awaiting Task
  30. Calling TaskCompletionSource.SetResult in a non blocking manner

Leave a Comment