2.2.2.7 Generic Service Response Payload
All DSLR two-way service requests follow the same convention for their responses. The message tag and payload is a child of the DSLR dispatch response tag defined in section 2.2.2.2 and includes the result of the function call and any output parameters returned by the function.
The format for a generic service response message payload (the function's return value and output parameters, if any) is as follows:
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Result |
|||||||||||||||||||||||||||||||
SerializedArgument_1 (variable) |
|||||||||||||||||||||||||||||||
... |
|||||||||||||||||||||||||||||||
SerializedArgument_N (variable) |
|||||||||||||||||||||||||||||||
... |
Result (4 bytes): An unsigned 32-bit integer containing the HRESULT returned from the function call. This can be any of the pre-defined DSLR error codes (see section 2.2.2.5) or a service-defined set of HRESULT codes.
SerializedArgument_1 (variable): An out argument (if any) if the call was successful. This parameter is defined by the service. See section 2.2.2.6 about valid data types for out parameters.
SerializedArgument_N (variable): Additional out arguments (if any) if the call was successful. These parameters are defined by the service. See section 2.2.2.6 about valid data types for out parameters.