Which way is preferred when doing asynchronous WCF calls?

I would not use the final version because it will run the operation on a worker thread instead of an I/O thread. This is especially bad if you're doing it inside ASP. NET, where the worker threads are needed to serve requests.

Not to mention, you're still blocking on the main thread waiting for the task to finish when you check its Result so technically you're wasting two worker threads, or one worker and the UI.

Up vote 6 down vote favorite 1 share g+ share fb share tw.

When invoking a WCF service asynchronous there seems to be two ways it can be done. 1. WcfClient _client = new WcfClient(); public void One() { _client.

BegindoSearch("input", ResultOne, null); } private void ResultOne(IAsyncResult ar) { string data = _client. EnddoSearch(ar); } 2. Public void Two() { WcfClient client = new WcfClient(); client.

DoSearchCompleted += TwoCompleted; client. DoSearchAsync("input"); } void TwoCompleted(object sender, doSearchCompletedEventArgs e) { string data = e. Result; } And with the new Task class we have an easy third way by wrapping the synchronous operation in a task.

3. Public void Three() { WcfClient client = new WcfClient(); var task = Task.Factory. StartNew(() => client.

DoSearch("input")); string data = task. Result; } They all give you the ability to execute other code while you wait for the result, but I think Task gives better control on what you execute before or after the result is retrieved. Are there any advantages or disadvantages to using one over the other?

Or scenarios where one way of doing it is more preferable? C# .net wcf asynchronous . Net-4.0 link|improve this question edited Apr 10 '10 at 21:18 asked Apr 10 '10 at 20:20Mikael Svenson10.9k822 100% accept rate.

I would not use the final version because it will run the operation on a worker thread instead of an I/O thread. This is especially bad if you're doing it inside ASP. NET, where the worker threads are needed to serve requests.

Not to mention, you're still blocking on the main thread waiting for the task to finish when you check its Result, so technically you're wasting two worker threads, or one worker and the UI. The BeginXYZ and XyzAsync methods for WCF clients work essentially the same way - you should choose the appropriate version based on the use case you want to support (either APC or event-driven, respectively). For example, the BeginXyz version would (perhaps counterintuitively) be easier to use within an ASP.

NET (or MVC) async page, whereas the XyzAsync version would be easier to use in a Windows Form.

The Worker vs IO thread aspect is interesting. I know the thread pool has a fixed amount of each one and that you can change them. But what's the difference between a worker thread and IO thread in the framework.

I assume it's more than just semantics. – Mikael Svenson Apr 10 '10 at 21:16 @Mikael: I/O threads are designed for long waiting periods; they basically go to sleep and wait for the I/O system to wake them back up with an interrupt. Worker threads are intended for CPU-heavy work, and you don't want to waste them on blocking synchronous I/O calls.

– Aaronaught Apr 10 '10 at 21:26 there's some more information in this MSDN article about tasks with respect to worker threads - msdn.microsoft.com/en-us/magazine/ff9592... - also a good background (kind of a history lesson) about the different async methods available in . NET – Simon_Weaver Sep 13 '10 at 3:17.

There's a problem with your first example. You should certainly not be creating a new WcfClient instance when you call EndDoSearch. You should either keep the original instance around in a field or pass it as the state parameter.

But in general, I prefer option #1 because it makes it very easy to use an anonymous method to handle the result. Var client = new WcfClient(); client. BeginDoSearch("input", ar => { var result = client.

EndDoSearch(ar); // blah blah }, null).

Good catch on that; mind you, it's iffy to be creating WCF clients on-the-fly period - usually these end up being singletons/per-session or managed by a DI container. – Aaronaught Apr 10 '10 at 20:53 @Josh, I know I should be using the same client, and have corrected it now :) – Mikael Svenson Apr 10 '10 at 21:11.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.