Calling async methods from a WCF service

by

Whether the server is using sync or async code does not matter for the client. Client and server are separated by a well-specified wire-protocol (often SOAP). SOAP has no notion of asynchronous completion.

You can have a sync server and an async client, or vice versa. The client cannot even detect whether the server is sync or async. This is an implementation detail. The server could be a wrist watch running Linux and you still couldn’t tell.

The style of IO you use is an implementation detail and does not influence the bytes that go over the network.

So pick what you like. The client can still use async IO to access the server.

I’m not sure why this is such a surprise to people. In other contexts this seems very intuitive: You can have a asynchronous TCP server and a synchronous client. I can say new WebClient().DownloadString(url) and download a string synchronously from a web-server that is implemented in an asynchronous way. I cannot even tell what server software is running.

Use Fiddler to look at what goes over the wire when you make a WCF call. There is no notion of synchronous or asynchronous calls.

Under the hood, when you invoke a service asynchronously, the WCF client library using TCP sockets in an asynchronous way. When you invoke synchronously, TCP sockets are being used with blocking calls. That’s the entire difference.

WCF generated clients can be made to have asynchronous methods in addition to the synchronous methods. Select the “Generate asynchronous operations” option in the UI. Now you have both versions. Both fully functional.

Here’s how you can convince yourself of this with an experiment: Write a sync server, and call it both sync and async from the same .NET client. Now write a 2nd server asynchronously (in any style you like) and use the exact same client code to call it.

Task and IAsyncResult are not serializable over SOAP anyway so it cannot possibly be the case that a Task is transmitted to the client.

More Related Contents:

  1. Different forms of the WCF service contract interface
  2. How to limit the amount of concurrent async I/O operations?
  3. Nesting await in Parallel.ForEach [duplicate]
  4. WaitAll vs WhenAll
  5. HttpClient.GetAsync(…) never returns when using await/async
  6. Running multiple async tasks and waiting for them all to complete
  7. Calling async method synchronously
  8. Entity Framework async operation takes ten times as long to complete
  9. Why does this async action hang when I try and access the Result property of my Task?
  10. Task sequencing and re-entracy
  11. How to wait for async method to complete?
  12. Pattern for calling WCF service using async/await
  13. Asynchronous Task.WhenAll with timeout
  14. Is there some way to handle async/await behind an ASMX service?
  15. Async call with await in HttpClient never returns
  16. Async and await – difference between console, Windows Forms and ASP.NET
  17. Await in catch block
  18. Why use async and return await, when you can return Task directly?
  19. async await return Task
  20. Executing tasks in parallel
  21. Proper way to start and fire-and-forget asynchronous calls?
  22. Use Task.Run() in synchronous method to avoid deadlock waiting on async method?
  23. A pattern for self-cancelling and restarting task
  24. A pattern to pause/resume an async task?
  25. Converting async/await to Task.ContinueWith
  26. How to Async Files.ReadAllLines and await for results?
  27. I thought await continued on the same thread as the caller, but it seems not to
  28. How do I create a custom SynchronizationContext so that all continuations can be processed by my own single-threaded event loop?
  29. Using async / await with DataReader ? ( without middle buffers!)
  30. Timeout pattern on task-based asynchronous method in C#

Leave a Comment