Saturday, February 04, 2006
Stunning results with multi-threaded application development
Wow ... I've just spent some time today studying multi-threaded application development, and have been absolutely amazed with the results from the multi-threaded test program I created. What kills me most about this new discovery of mine is how easy it is to spawn additional worker threads to make your application more responsive. Here's a great example of how you could use multi-threading: if your application is accessing data from a remote computer on a slow WAN link, you can tell you app to spawn a new thread for the data access, while your main user interface window can continue on in perfect bliss! This is almost exactly what I'm doing with my current test application when connecting to the WMI service on a remote computer. Additionally, since you can specify a different priority for a new thread, this is perfect for times you're running a particularly hefty (lower-priority) WMI query in the background and don't want to make your app lock up while it's in progress. In my future development of a computer management application, I will be sure to take advantage of this awesome, yet easily-implemented feature.
FYI: Don't forget to leave out the parentheses when you're specifying a delegate method, otherwise it'll think you're trying to call the function and give the the following compile-time error: "Method name expected"
¶ 5:28 PM
FYI: Don't forget to leave out the parentheses when you're specifying a delegate method, otherwise it'll think you're trying to call the function and give the the following compile-time error: "Method name expected"
¶ 5:28 PM
