| | |
|---|
| | | |
|---|
| | | ##### Parsing |
|---|
| | | | Name | Description | Type | |
|---|
| | | |----------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| |
|---|
| | | |----------------|---------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| |
|---|
| | | | ... | See [Base Packet Format](#base-packet-format) for parsing the prologue of a request packet. | ... | |
|---|
| | | | Call ID | The nonce token for this call to identify the response associated with this request. | `u32` | |
|---|
| | | | Method Name | The method to call on the server. | [`String`](./03_rendezvous_structure.md#structure-string) | |
|---|
| | | | Class Versions | Version information about the data in the request | [`List`](./03_rendezvous_structure.md#structure-listt)`<`[`ClassVersion`](#structure-classversion)`>` | |
|---|
| | | | Request Data | Raw data to pass to the request handler, see the respective [protocol and method specification](#known-protocols) to write and read this. | `<remaining bytes>` | |
|---|
| | | | ... | See the respective [protocol and method specification](#known-protocols) to parse and write the rest of the packet. | | |
|---|
| | | |
|---|
| | | ### Structure: `ClassVersion` |
|---|
| | | Example: |
|---|
| | |
|---|
| | | |
|---|
| | | ##### Parsing |
|---|
| | | | Name | Description | Type | |
|---|
| | | |---------------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| |
|---|
| | | |-------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| |
|---|
| | | | ... | See [Response Packet Format](#response-packet-format) for parsing the prologue of a successful response packet. | ... | |
|---|
| | | | Call ID | The nonce token for the call to associate the response to the request. | `u32` | |
|---|
| | | | Method Name | The method that was called by the client. | [`String`](./03_rendezvous_structure.md#structure-string) | |
|---|
| | | | Response Data | Raw data to pass to the response handler, see the respective [protocol and method specification](#known-protocols) to write and read this. | `<remaining bytes>` | |
|---|
| | | | Method Name | The method that was called by the client, see note below. | [`String`](./03_rendezvous_structure.md#structure-string) | |
|---|
| | | | ... | See the respective [protocol and method specification](#known-protocols) to parse and write the rest of the packet. | | |
|---|
| | | |
|---|
| | | > [!NOTE] |
|---|
| | | > Typically, a `*` is appended to the Method Name in responses for currently unknown reasons. Likely to do with the fact that the response handlers update pointers to data containers created in the original request. |
|---|
| | | > |
|---|
| | | > For example, where the request might be `LoginProtocol::LoginWithToken_V1`, the response would be for `LoginProtocol::LoginWithToken_V1*`. |
|---|
| | | |
|---|
| | | ### Unsuccessful Response Format |
|---|
| | | |
|---|
