Click here to Skip to main content
Click here to Skip to main content

Simple Worker Thread Class

By , 5 May 2009
 

Introduction

Many times we need to create worker threads and generally we want to wait in the main thread till all worker threads finish their execution, something similar to pthread’s pthread_join call. We want some notification on the completion of worker thread; check the status of the worker thread if it is still executing in thread function or finished, etc. Also sometimes we want to keep the worker thread alive even on completion of thread function so that we can resubmit a different job (typically in a thread pool). All these things can be done with event objects by managing their state to signalled non signaled, etc. It is difficult to manage such code using different event objects. I consolidated all this commonly used worker thread functionality in a basic implementation of WorkerThread class.

WorkerThread Class

WorkerThread is a basic implementation for worker thread with PostThreadMessage, Join, RegisterOnCompleteRoutine and thread execution status. It can be enhanced further for many other features but I want to keep the idea simple. Here my main focus is just to show how to use a PostThreadMessage for worker threads.

Using the Code

Using WorkerThread class in your existing application is very simple. You just need to add WorkerThread.cpp in your project and include WorkerThread.h where you want to use this class.

Add variables of WorkerThread class wherever you want to create a worker thread. Create a worker thread using Start() with an optional auto quit parameter (default is true) and to end the thread, use End() method. If auto quit parameter is true, there is no need to call End() method of WorkerThread class. Join() method will simply cause calling thread to wait till work thread finishes its execution. GetStatus() will let you know the current thread status (NotCreated, Created, Started, Restarted, Complete). ReExecute() method can be used only for non auto quit threads (created with false parameter in constructor) with different or same data (this can be further enhanced to avoid overwriting the data). RegisterOnCompleteRoutine() method can be used to register an optional routine that will be called on completion of thread function.

Below is the sample code to show the usage of the WorkerThread class:

#include "stdafx.h"
#include "WorkerThread.h"

#define MAXCOUNT 5

DWORD WINAPI ThreadProc(void *param)
{
    int i = (int)param;
    //
    // your code
    //
    
    return 0;
}

DWORD WINAPI OnComplete(void *param)
{
    int i = (int)param;

    printf("OnComplete data = %d\n", i);

    return 0;
}

int _tmain(int argc, _TCHAR* argv[])
{
    // Create few worker threads with autoQuit false
    WorkerThread workerThread[MAXCOUNT] = {false, false, false, false, false};

    // Register an optional completion routine
    workerThread[2].RegisterOnCompleteRoutine(OnComplete, (void *)1234);

    // Start all of them
    for (int i = 0; i < MAXCOUNT; ++i) {
        if (workerThread[i].Start(ThreadProc, (void *)i)) {
            printf("Started %d\n", i);
        }
    }

    for (int i = 0; i < MAXCOUNT; ++i) {
        if (workerThread[i].ReExecute((void *)i)) {
            printf("Restarted %d\n", i);
        }

    }

    for (int i = 0; i < MAXCOUNT; ++i) {
        workerThread[i].End();
    }

    // main thread will wait here, till all others finish.
    for (int i = 0; i < MAXCOUNT; ++i) {
        workerThread[i].Join();
    }

    return 0;
}        

Points of Interest

Note the dummy PeekMessage() call in starting of ThreadProc(), just for force creation of a message queue for our worker thread.

History

  • 5th May, 2009: Initial revision

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Manish K. Agarwal
Team Leader Pitney Bowes
India India
Member
Working with Pitney Bowes, Noida (India). Using C/C++, VC++, MFC, STL, C#, Java etc. on various platform like Windows, Unix, Macintosh etc. from last 12 years to convert various type of requirements into running software components. My core expertise is multithreaded desktop product development on Windows.

Sign Up to vote   Poor Excellent
Add a reason or comment to your vote: x
Votes of 3 or less require a comment

Comments and Discussions

 
Hint: For improved responsiveness ensure Javascript is enabled and choose 'Normal' from the Layout dropdown and hit 'Update'.
You must Sign In to use this message board.
Search this forum  
    Spacing  Noise  Layout  Per page   
QuestionMy vote 5memberShlabh Sharma27 Sep '11 - 2:19 
GeneralMy vote of 1memberMike O'Neill12 May '09 - 8:01 
The class jumbles together two distinctly different communication/sysnchronization paradigms: messages and events. If a thread has a message queue that it's servicing, use messaging for inter-thread communication and for synchronization. There is no point in complicating matters by trying to use both.
 
The class also uses the highly unreliable PostThreadMessage. Per MSDN documentation of this function, if the thread hosts any visible windows, PostThreadMessage is practically guaranteed to lose messages. It might be OK to use PostThreadMessage if the thread is a pure worker-style thread, but the article doesn't warn against use of the thread to host a window.
GeneralRe: My vote of 1memberManish K. Agarwal12 May '09 - 18:17 
GeneralMy vote of 1memberRick York6 May '09 - 6:46 
GeneralRe: My vote of 1memberManish K. Agarwal7 May '09 - 18:50 
GeneralRe: My vote of 1membergeoyar12 May '09 - 11:51 
GeneralMy vote of 1memberJohann Gerell5 May '09 - 20:57 
GeneralRe: My vote of 1membervampyr5 May '09 - 21:39 
GeneralRe: My vote of 1memberManish K. Agarwal5 May '09 - 23:52 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Permalink | Advertise | Privacy | Mobile
Web02 | 2.6.130516.1 | Last Updated 5 May 2009
Article Copyright 2009 by Manish K. Agarwal
Everything else Copyright © CodeProject, 1999-2013
Terms of Use
Layout: fixed | fluid