2.2.2.3.4 Read Reply Message
The client responds to the read file request from the server with this message.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Header |
|||||||||||||||||||||||||||||||
|
Result |
|||||||||||||||||||||||||||||||
|
cbBytesRead |
|||||||||||||||||||||||||||||||
|
Data (variable) |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
UnusedByte |
|||||||||||||||||||||||||||||||
Header (4 bytes): A CLIENT_IO_HEADER reply header. The PacketType field MUST be set to RESPONSE_PACKET (0x00). The RequestId field MUST match the value in the RequestId field in the corresponding Read Request Message.
Result (4 bytes): An HRESULT that describes the result of the read operation. There are no specific HRESULT values expected by this protocol because the value is returned by the client-side device when it completes the Read Request. The possible values will vary depending on the device.
cbBytesRead (4 bytes): A 32-bit unsigned integer. This field specifies the number of bytes read.
Data (variable): An array of bytes. A variable-length field that MUST contain the data read from the client.
UnusedByte (1 byte): An 8-bit unsigned integer. This field is unused and MUST be ignored.