.NET makes it relatively easy to add multithreading capabilities to your applications. Do you think this feature will be used effectively by most programmers or misused and abused? If you're not already using multithreading in .NET, did this article help you get started? What problems or issues have you had with multithreaded applications? Let us know in the dotnet.clr. general discussion group.
Have you ever built an application where users had to wait while the application performed some lengthy calculation or operation? Learn how to improve your application's responsiveness by creating and controlling threads.
by Peter G. Aitken
October 21, 2002
The concept of threads is central to the inner workings of most operating systems, including Windows, but relatively few programmers even know what they are—let alone how to take advantage of them. Understanding threads, using modern operating system's multithreading capabilities properly, is a fundamental step toward creating fast, responsive applications. The .NET Framework makes creating multi-threaded applications easier than ever. In this article you'll see what threads are, how threading works, and how you can use them in your applications.
Why Multithreading?
To understand the power of multithreading you need to know something about how the Windows operating system works under the hood. Windows is a preemptive multitasking operating system. The system CPU can do only one thing at a time, but to give the illusion that multiple processes are running simultaneously the operating system splits the CPU time between the various running processes.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
