2.2.2.1 DVC Create Request PDU (DYNVC_CREATE_REQ)
The DYNVC_CREATE_REQ (section 2.2.2.1) PDU is sent by the DVC server manager to the DVC client manager to request that a channel be opened.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
cbId |
Pri |
Cmd |
ChannelId (variable) |
||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
ChannelName (variable) |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
cbId (2 bits): Indicates the length of the ChannelId field.
-
Value
Meaning
0x00
The ChannelId field length is 1 byte.
0x01
The ChannelId field length is 2 bytes.
0x02
The ChannelId field length is 4 bytes.
0x03
Invalid value.
Pri (2 bits): Version 1 of the Remote Desktop Protocol: Dynamic Virtual Channel Extension (as specified in section 2.2.1.1.1) does not support priority classes. The client SHOULD ignore this field.
-
In version 2 of the Remote Desktop Protocol: Dynamic Virtual Channel Extension, this field specifies the priority class for the channel that is being created, with the Pri field values 0, 1, 2, and 3 corresponding to PriorityCharge0, PriorityCharge1, PriorityCharge2, and PriorityCharge3, as specified in section 2.2.1.1.2. The method of determining priority class is the same for both client to server data and server to client data.
Cmd (4 bits): MUST be set to 0x01 (Create).
ChannelId (variable): A variable-length 8-bit, 16-bit, or 32-bit unsigned integer. This is a server-generated identifier for the channel being created. The DVC server manager MUST ensure that this number is unique within a static virtual channel connection.
ChannelName (variable): A null-terminated ANSI encoded character string. The name of the listener on the TS client with which the TS server application is requesting that a channel be opened.