|
namespace TaskManagerDemo.Utility
{
/// <summary>
/// This class wraps TaskManager and renames it for the sole purpose of making one of its important uses more obvious.
/// In general, a high-level task that aggregates several AsyncServiceCallManager objects should be represented by a
/// TaskManager oject, whereas each sub-task that relates to calling an async service method and processing its results
/// via an ...AsyncCompleted event handler should be represented by an AsyncServiceCallManager. The two classes are
/// functionally interchangeable but using objects of the respective classes as recommended here serves a documentary
/// purpose.
/// </summary>
public class AsyncServiceCallManager : TaskManager
{
public AsyncServiceCallManager(string name) : base(name) { }
}
}
|
By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.
George Henry has worked as a software developer for more than 20 years. He is currently employed by Concur in Bellevue, Washington, USA.