2.2.1 Socket Connect Header
The Socket Connect header specifies the connection type of a socket connection to be established. It has the following structure.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
SessionID |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
ConnectionType |
Reserved1 |
A |
Reserved2 |
||||||||||||||||||||||||||||
SessionID (8 bytes): The ID of the Session object. At the conclusion of the session exchange, each peer has a Session object, and the two Session objects' SessionID fields match. It is used by the Share Receiver to find the correct Session object to associate with the inbound socket.
ConnectionType (1 byte): The connection type of the socket connection to be established, from the Connection Type Enumeration (section 2.2.5).
Reserved1 (2 bytes): This field MUST be set to zero when sent and MUST be ignored when received.
A (1 bit): The Abort flag. A client sets this flag in order to indicate to the server that the client is required to terminate the session immediately. This flag is useful when, for example, the user has decided not to accept a socket or share connection.
Reserved2 (7 bits): This field MUST be set to zero when sent and MUST be ignored when received.