REQUESTDATA: Difference between revisions
No edit summary |
mNo edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Request data | |||
Request data | |||
=== Type === | === Type === | ||
[[ | [[PID]] pid | ||
[[ | [[ULONG]] ulData | ||
==== C Declaration Method ==== | ==== C Declaration Method ==== | ||
| Line 10: | Line 9: | ||
=== Fields === | === Fields === | ||
;pid | ;pid:Process identifier of the process that placed the element into the queue. | ||
:Process identifier of the process that placed the element into the queue. | ;ulData:An event code that is specified by the application. This data is understood by both the thread that is adding the element to the queue (the client thread) and the thread that receives the queue element (server thread). It has no special meaning, and is not altered by the operating system. | ||
;ulData | |||
:An event code that is specified by the application. This data is understood by both the thread that is adding the element to the queue (the client thread) and the thread that receives the queue element (server thread). It has no special meaning, and is not altered by the operating system. | |||
[[Category: | [[Category:Data type]] | ||
Latest revision as of 20:59, 13 March 2019
Request data
Type
PID pid ULONG ulData
C Declaration Method
typedef struct
Fields
- pid
- Process identifier of the process that placed the element into the queue.
- ulData
- An event code that is specified by the application. This data is understood by both the thread that is adding the element to the queue (the client thread) and the thread that receives the queue element (server thread). It has no special meaning, and is not altered by the operating system.