2.2.7.2 MILCMD_TRANSPORT_ROUNDTRIPREQUEST
The MILCMD_TRANSPORT_ROUNDTRIPREQUEST packet requests a notification message to be sent by the client when the current batch has been processed, composed and presented, and the resulting frame has appeared on the screen. The client MUST respond with a MILMSG_NOTIFYROUNDTRIPREPLY notification. This message/notification pair differs from MILCMD_TRANSPORT_SYNCFLUSH and MILMSG_SYNCFLUSHREPLY only if the graphics system running on the client behaves asynchronously from the composition engine. In that case, the reply to this message MUST wait the additional time between frame presentation and actual frame appearance on the screen.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
messageSize |
|||||||||||||||||||||||||||||||
|
controlCode |
|||||||||||||||||||||||||||||||
|
RequestUniquenessId |
|||||||||||||||||||||||||||||||
messageSize (4 bytes): A 32-bit unsigned integer. The size of this message in bytes. The value of this field MUST be set to 0x0000000C.
controlCode (4 bytes): A 32-bit unsigned integer containing the control code for this message. The value of this field MUST be equal to 0x00000003.
RequestUniquenessId (4 bytes): A 32-bit unsigned integer. A 32-bit numeric identifier that is meant to be used by the server as a request context handle. When responding to a round trip request with a MILMSG_NOTIFYROUNDTRIPREPLY notification, the client MUST use the identifier used by the server to send the matching round trip request.