 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The CMsgThreadclass provides support for a worker thread to which requests can be posted asynchronously instead of sent directly.
The CAMThreadclass provides a worker thread to which single requests can be sent.
Only one client can make a request at a time, and the client blocks until the worker thread has completed the request. By contrast, the CMsgThreadclass provides a worker thread to which any number of requests can be posted.
The requests (in the form of a CMsgobject) are queued and executed in order, asynchronously.
No reply or return value is received.
Data Members
| Member | Description |
|---|---|
|
dwFlags |
Flag parameter to the request code. |
|
lpParam |
Data required by the worker thread as parameter or return values. This data should not be stack-based, because it is referenced some time after completing the queuing operation. |
|
pEvent |
Event object that a worker thread can signal to indicate the completion of the operation. |
|
uMsg |
Request code that is defined by the client of the thread class and understood by the overridden worker thread function. |
Member Functions
| Member function | Description |
|---|---|
|
Constructs a CMsgobject. |
Requirements
| Windows Embedded CE | Windows CE 2.12 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |
| Note | Microsoft DirectShow applications and DirectShow filters have
different include file and Library requirements
For more information, see Setting Up the Build Environment |