| durin42 |
| hg-reviewers |
We may eventually want a separate frame type for this. But for
now this is the easiest to implement.
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
| Path | Packages | |||
|---|---|---|---|---|
| M | mercurial/help/internals/wireprotocol.txt (14 lines) | |||
| M | mercurial/wireprotoframing.py (2 lines) |
| Command data continuation. When set, the data for this command | Command data continuation. When set, the data for this command | ||||
| continues into a subsequent frame. | continues into a subsequent frame. | ||||
| 0x02 | 0x02 | ||||
| End of data. When set, command data has been fully sent to the | End of data. When set, command data has been fully sent to the | ||||
| server. The command has been fully issued and no new data for this | server. The command has been fully issued and no new data for this | ||||
| command will be sent. The next frame will belong to a new command. | command will be sent. The next frame will belong to a new command. | ||||
| Bytes Response Data (``0x04``) | Response Data (``0x04``) | ||||
| ------------------------------ | ------------------------ | ||||
| This frame contains raw bytes response data to an issued command. | This frame contains raw response data to an issued command. | ||||
| The following flag values are defined for this type: | The following flag values are defined for this type: | ||||
| 0x01 | 0x01 | ||||
| Data continuation. When set, an additional frame containing raw | Data continuation. When set, an additional frame containing response data | ||||
| response data will follow. | will follow. | ||||
| 0x02 | 0x02 | ||||
| End of data. When sent, the response data has been fully sent and | End of data. When set, the response data has been fully sent and | ||||
| no additional frames for this response will be sent. | no additional frames for this response will be sent. | ||||
| 0x04 | |||||
| CBOR data. When set, the frame payload consists of CBOR data. | |||||
| The ``0x01`` flag is mutually exclusive with the ``0x02`` flag. | The ``0x01`` flag is mutually exclusive with the ``0x02`` flag. | ||||
| Error Response (``0x05``) | Error Response (``0x05``) | ||||
| ------------------------- | ------------------------- | ||||
| An error occurred when processing a request. This could indicate | An error occurred when processing a request. This could indicate | ||||
| a protocol-level failure or an application level failure depending | a protocol-level failure or an application level failure depending | ||||
| FLAGS_COMMAND_DATA = { | FLAGS_COMMAND_DATA = { | ||||
| b'continuation': FLAG_COMMAND_DATA_CONTINUATION, | b'continuation': FLAG_COMMAND_DATA_CONTINUATION, | ||||
| b'eos': FLAG_COMMAND_DATA_EOS, | b'eos': FLAG_COMMAND_DATA_EOS, | ||||
| } | } | ||||
| FLAG_BYTES_RESPONSE_CONTINUATION = 0x01 | FLAG_BYTES_RESPONSE_CONTINUATION = 0x01 | ||||
| FLAG_BYTES_RESPONSE_EOS = 0x02 | FLAG_BYTES_RESPONSE_EOS = 0x02 | ||||
| FLAG_BYTES_RESPONSE_CBOR = 0x04 | |||||
| FLAGS_BYTES_RESPONSE = { | FLAGS_BYTES_RESPONSE = { | ||||
| b'continuation': FLAG_BYTES_RESPONSE_CONTINUATION, | b'continuation': FLAG_BYTES_RESPONSE_CONTINUATION, | ||||
| b'eos': FLAG_BYTES_RESPONSE_EOS, | b'eos': FLAG_BYTES_RESPONSE_EOS, | ||||
| b'cbor': FLAG_BYTES_RESPONSE_CBOR, | |||||
| } | } | ||||
| FLAG_ERROR_RESPONSE_PROTOCOL = 0x01 | FLAG_ERROR_RESPONSE_PROTOCOL = 0x01 | ||||
| FLAG_ERROR_RESPONSE_APPLICATION = 0x02 | FLAG_ERROR_RESPONSE_APPLICATION = 0x02 | ||||
| FLAGS_ERROR_RESPONSE = { | FLAGS_ERROR_RESPONSE = { | ||||
| b'protocol': FLAG_ERROR_RESPONSE_PROTOCOL, | b'protocol': FLAG_ERROR_RESPONSE_PROTOCOL, | ||||
| b'application': FLAG_ERROR_RESPONSE_APPLICATION, | b'application': FLAG_ERROR_RESPONSE_APPLICATION, | ||||