{"id":55931,"date":"2010-04-05T10:00:00","date_gmt":"2010-04-05T10:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/pfxteam\/2010\/04\/05\/parallelextensionsextras-tour-3-additional-task-extensions-methods\/"},"modified":"2010-04-05T10:00:00","modified_gmt":"2010-04-05T10:00:00","slug":"parallelextensionsextras-tour-3-additional-task-extensions-methods","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/parallelextensionsextras-tour-3-additional-task-extensions-methods\/","title":{"rendered":"ParallelExtensionsExtras Tour – #3 – Additional Task Extensions Methods"},"content":{"rendered":"

(The full set of ParallelExtensionsExtras Tour posts is available <\/em>here<\/em><\/font><\/a>.)<\/em>  <\/font><\/p>\n

In our last ParallelExtensionsExtras tour post<\/a>, we discussed implementing an extension ToObservable method for Task<TResult>.  <\/span>This is just one of a myriad of extra pieces of functionality that are useful with Tasks, and the TaskExtrasExtensions.cs file in <\/font>ParallelExtensionsExtras<\/font><\/a> includes several.  <\/span>In this post, we’ll cover a few of the more interesting ones.<\/p>\n

<\/font><\/font><\/p>\n

WithTimeout<\/p>\n

<\/font><\/font><\/b><\/p>\n

When dealing with operations that run asynchronously, it’s not uncommon to want to incorporate a timeout, such that other code that depends on the asynchronous operation isn’t forced to wait too long.  <\/span>We can tackle this use case with a simple WithTimeout method:<\/p>\n

<\/font><\/font><\/p>\n

public static Task<TResult> WithTimeout<TResult>(<\/p>\n

<\/font><\/p>\n

    <\/span>this Task<TResult> task, TimeSpan timeout)<\/p>\n

<\/font><\/p>\n

{<\/p>\n

<\/font><\/p>\n

    <\/span>var result = new TaskCompletionSource<TResult>(task.AsyncState);<\/p>\n

<\/font><\/p>\n

    <\/span>var timer = new Timer(_ => result.TrySetCanceled(), <\/p>\n

<\/font><\/p>\n

        <\/span>null, timeout, TimeSpan.FromMilliseconds(-1));<\/p>\n

<\/font><\/p>\n

    <\/span>task.ContinueWith(t =><\/p>\n

<\/font><\/p>\n

    <\/span>{<\/p>\n

<\/font><\/p>\n

        <\/span>timer.Dispose();<\/p>\n

<\/font><\/p>\n

        <\/span>result.TrySetFromTask(t);<\/p>\n

<\/font><\/p>\n

    <\/span>});<\/p>\n

<\/font><\/p>\n

    <\/span>return result.Task;<\/p>\n

<\/font><\/p>\n

}<\/p>\n

<\/font><\/p>\n

\n

 <\/font><\/p>\n<\/p>\n

This method works by creating a <\/font>TaskCompletionSource<\/font><\/a> to serve as the representation for the potentially timed-out task.  <\/span>A System.Threading.Timer instance is also created to fire once after the user specified period of time.  <\/span>When the timer does fire, it attempts to transition the TaskCompletionSource into a canceled state, which will only take effect if the TaskCompletionSource hasn’t already been completed.  <\/span>In addition, a continuation is used to dispose of the timer and to transition the TaskCompletionSource to a completed state when the original task finishes.<\/p>\n

<\/font><\/font><\/p>\n

TrySetFromTask is another utility extension method defined in ParallelExtensionsExtras that serves to wrap up some frequently needed logic when using a TaskCompletionSource to serve as a proxy for another Task<TResult>:<\/p>\n

<\/font><\/font><\/p>\n

public static bool TrySetFromTask<TResult>(<\/p>\n

<\/font><\/p>\n

    <\/span>this TaskCompletionSource<TResult> resultSetter, Task<TResult> task)<\/p>\n

<\/font><\/p>\n

{<\/p>\n

<\/font><\/p>\n

    <\/span>switch (task.Status)<\/p>\n

<\/font><\/p>\n

    <\/span>{<\/p>\n

<\/font><\/p>\n

        <\/span>case TaskStatus.RanToCompletion: <\/p>\n

<\/font><\/p>\n

            <\/span>return resultSetter.TrySetResult(task.Result);<\/p>\n

<\/font><\/p>\n

        <\/span>case TaskStatus.Faulted: <\/p>\n

<\/font><\/p>\n

            <\/span>return resultSetter.TrySetException(<\/p>\n

<\/font><\/p>\n

                <\/span>task.Exception.InnerExceptions);<\/p>\n

<\/font><\/p>\n

        <\/span>case TaskStatus.Canceled: <\/p>\n

<\/font><\/p>\n

           <\/span>return resultSetter.TrySetCanceled();<\/p>\n

<\/font><\/p>\n

        <\/span>default: <\/p>\n

<\/font><\/p>\n

           <\/span>throw new InvalidOperationException(“The task was not completed.”);<\/p>\n

<\/font><\/p>\n

    <\/span>}<\/p>\n

<\/font><\/p>\n

}<\/p>\n

<\/font><\/p>\n

\n

 <\/font><\/p>\n<\/p>\n

TrySetFromTask is defined in TaskCompletionSourceExtensions.cs<\/p>\n

<\/font><\/font><\/p>\n

WithAsyncCallback<\/p>\n

<\/font><\/font><\/b><\/p>\n

Tasks implement IAsyncResult, which make them useful in custom implementations of the Asnchronous Programming Model (APM) pattern.  <\/span>However, when implementing the APM pattern, there are some very important rules that need to be followed.  <\/span>For example, the object state parameter passed to the BeginXx method must be returned from the resulting IAsyncResult’s AsyncState property, the AsyncCallback passed to BeginXx must be invoked when the asynchronous operation completes, and it must be invoked with the exact same IAsyncResult returned from the BeginXx method as its argument.  <\/span>We can implement a WithAsyncCallback method to accomplish all of this:<\/p>\n

<\/font><\/font><\/p>\n

public static Task WithAsyncCallback(<\/p>\n

<\/font><\/p>\n

    <\/span>this Task task, AsyncCallback callback, object state)<\/p>\n

<\/font><\/p>\n

{<\/p>\n

<\/font><\/p>\n

    <\/span>var tcs = new TaskCompletionSource<object>(state);<\/p>\n

<\/font><\/p>\n

    <\/span>task.ContinueWith(_ =><\/p>\n

<\/font><\/p>\n

    <\/span>{<\/p>\n

<\/font><\/p>\n

        <\/span>tcs.TrySetFromTask(task);<\/p>\n

<\/font><\/p>\n

        <\/span>if (callback != null) callback(tcs.Task);<\/p>\n

<\/font><\/p>\n

    <\/span>});<\/p>\n

<\/font><\/p>\n

    <\/span>return tcs.Task;<\/p>\n

<\/font><\/p>\n

}<\/p>\n

<\/font><\/p>\n

\n

 <\/font><\/p>\n<\/p>\n

As with WithTimeout, a TaskCompletionSource instance is used, here to represent the IAsyncResult that should be both returned from BeginXx and passed to the AsyncCallback.  <\/span>When the source task completes, using ContinueWith we transfer the task’s results to the TaskCompletionSource and we then invoke the AsyncCallback.<\/font><\/font><\/p><\/p>\n","protected":false},"excerpt":{"rendered":"

(The full set of ParallelExtensionsExtras Tour posts is available here.)   In our last ParallelExtensionsExtras tour post, we discussed implementing an extension ToObservable method for Task<TResult>.  This is just one of a myriad of extra pieces of functionality that are useful with Tasks, and the TaskExtrasExtensions.cs file in ParallelExtensionsExtras includes several.  In this post, we’ll cover a […]<\/p>\n","protected":false},"author":360,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[7908],"tags":[7907,7911,7909,7924,7912],"class_list":["post-55931","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pfxteam","tag-net-4","tag-code-samples","tag-parallel-extensions","tag-parallelextensionsextras","tag-task-parallel-library"],"acf":[],"blog_post_summary":"

(The full set of ParallelExtensionsExtras Tour posts is available here.)   In our last ParallelExtensionsExtras tour post, we discussed implementing an extension ToObservable method for Task<TResult>.  This is just one of a myriad of extra pieces of functionality that are useful with Tasks, and the TaskExtrasExtensions.cs file in ParallelExtensionsExtras includes several.  In this post, we’ll cover a […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/55931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/360"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=55931"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/55931\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=55931"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=55931"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=55931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}