# HG changeset patch # User Gregory Szorc # Date 1521061072 25200 # Node ID 61393f888dfe8b4f5e729f4ac105dbe14a620f53 # Parent e7a012b60d6ed96819a48142bf07428aa13c7589 wireproto: define and implement responses in framing protocol Previously, we only had client-side frame types defined. This commit defines and implements basic support for server-side frame types. We introduce two frame types - one for representing the raw bytes result of a command and another for representing error results. The types are quite primitive and behavior will expand over time. But you have to start somewhere. Our server reactor gains methods to react to an intent to send a response. Again, following the "sans I/O" pattern, the reactor doesn't actually send the data. Instead, it gives the caller a generator to frames that it can send out over the wire. Differential Revision: https://phab.mercurial-scm.org/D2858 diff -r e7a012b60d6e -r 61393f888dfe mercurial/help/internals/wireprotocol.txt --- a/mercurial/help/internals/wireprotocol.txt Wed Mar 14 13:32:31 2018 -0700 +++ b/mercurial/help/internals/wireprotocol.txt Wed Mar 14 13:57:52 2018 -0700 @@ -591,6 +591,40 @@ 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. +Bytes Response Data (``0x04``) +------------------------------ + +This frame contains raw bytes response data to an issued command. + +The following flag values are defined for this type: + +0x01 + Data continuation. When set, an additional frame containing raw + response data will follow. +0x02 + End of data. When sent, the response data has been fully sent and + no additional frames for this response will be sent. + +The ``0x01`` flag is mutually exclusive with the ``0x02`` flag. + +Error Response (``0x05``) +------------------------- + +An error occurred when processing a request. This could indicate +a protocol-level failure or an application level failure depending +on the flags for this message type. + +The payload for this type is an error message that should be +displayed to the user. + +The following flag values are defined for this type: + +0x01 + The error occurred at the transport/protocol level. If set, the + connection should be closed. +0x02 + The error occurred at the application level. e.g. invalid command. + Issuing Commands ---------------- diff -r e7a012b60d6e -r 61393f888dfe mercurial/wireprotoframing.py --- a/mercurial/wireprotoframing.py Wed Mar 14 13:32:31 2018 -0700 +++ b/mercurial/wireprotoframing.py Wed Mar 14 13:57:52 2018 -0700 @@ -25,11 +25,15 @@ FRAME_TYPE_COMMAND_NAME = 0x01 FRAME_TYPE_COMMAND_ARGUMENT = 0x02 FRAME_TYPE_COMMAND_DATA = 0x03 +FRAME_TYPE_BYTES_RESPONSE = 0x04 +FRAME_TYPE_ERROR_RESPONSE = 0x05 FRAME_TYPES = { b'command-name': FRAME_TYPE_COMMAND_NAME, b'command-argument': FRAME_TYPE_COMMAND_ARGUMENT, b'command-data': FRAME_TYPE_COMMAND_DATA, + b'bytes-response': FRAME_TYPE_BYTES_RESPONSE, + b'error-response': FRAME_TYPE_ERROR_RESPONSE, } FLAG_COMMAND_NAME_EOS = 0x01 @@ -58,11 +62,29 @@ b'eos': FLAG_COMMAND_DATA_EOS, } +FLAG_BYTES_RESPONSE_CONTINUATION = 0x01 +FLAG_BYTES_RESPONSE_EOS = 0x02 + +FLAGS_BYTES_RESPONSE = { + b'continuation': FLAG_BYTES_RESPONSE_CONTINUATION, + b'eos': FLAG_BYTES_RESPONSE_EOS, +} + +FLAG_ERROR_RESPONSE_PROTOCOL = 0x01 +FLAG_ERROR_RESPONSE_APPLICATION = 0x02 + +FLAGS_ERROR_RESPONSE = { + b'protocol': FLAG_ERROR_RESPONSE_PROTOCOL, + b'application': FLAG_ERROR_RESPONSE_APPLICATION, +} + # Maps frame types to their available flags. FRAME_TYPE_FLAGS = { FRAME_TYPE_COMMAND_NAME: FLAGS_COMMAND, FRAME_TYPE_COMMAND_ARGUMENT: FLAGS_COMMAND_ARGUMENT, FRAME_TYPE_COMMAND_DATA: FLAGS_COMMAND_DATA, + FRAME_TYPE_BYTES_RESPONSE: FLAGS_BYTES_RESPONSE, + FRAME_TYPE_ERROR_RESPONSE: FLAGS_ERROR_RESPONSE, } ARGUMENT_FRAME_HEADER = struct.Struct(r' HTTP/1.1 200 OK\r\n s> Server: testing stub value\r\n s> Date: $HTTP_DATE$\r\n - s> Content-Type: text/plain\r\n - s> Content-Length: 29\r\n + s> Content-Type: application/mercurial-exp-framing-0001\r\n + s> Transfer-Encoding: chunked\r\n s> \r\n - s> customreadonly bytes response + s> 21\r\n + s> \x1d\x00\x00Bcustomreadonly bytes response + s> \r\n + s> 0\r\n + s> \r\n Request to read-write command fails because server is read-only by default @@ -302,10 +306,14 @@ s> HTTP/1.1 200 OK\r\n s> Server: testing stub value\r\n s> Date: $HTTP_DATE$\r\n - s> Content-Type: text/plain\r\n - s> Content-Length: 29\r\n + s> Content-Type: application/mercurial-exp-framing-0001\r\n + s> Transfer-Encoding: chunked\r\n s> \r\n - s> customreadonly bytes response + s> 21\r\n + s> \x1d\x00\x00Bcustomreadonly bytes response + s> \r\n + s> 0\r\n + s> \r\n Authorized request for unknown command is rejected diff -r e7a012b60d6e -r 61393f888dfe tests/test-wireproto-serverreactor.py --- a/tests/test-wireproto-serverreactor.py Wed Mar 14 13:32:31 2018 -0700 +++ b/tests/test-wireproto-serverreactor.py Wed Mar 14 13:57:52 2018 -0700 @@ -79,6 +79,10 @@ self.assertIsInstance(res[1], dict) self.assertEqual(res[0], expected) + def assertframesequal(self, frames, framestrings): + expected = [ffs(s) for s in framestrings] + self.assertEqual(list(frames), expected) + def test1framecommand(self): """Receiving a command in a single frame yields request to run it.""" reactor = makereactor() @@ -270,6 +274,42 @@ 'message': b'command data frame without flags', }) + def testsimpleresponse(self): + """Bytes response to command sends result frames.""" + reactor = makereactor() + list(sendcommandframes(reactor, b'mycommand', {})) + + result = reactor.onbytesresponseready(b'response') + self.assertaction(result, 'sendframes') + self.assertframesequal(result[1]['framegen'], [ + b'bytes-response eos response', + ]) + + def testmultiframeresponse(self): + """Bytes response spanning multiple frames is handled.""" + first = b'x' * framing.DEFAULT_MAX_FRAME_SIZE + second = b'y' * 100 + + reactor = makereactor() + list(sendcommandframes(reactor, b'mycommand', {})) + + result = reactor.onbytesresponseready(first + second) + self.assertaction(result, 'sendframes') + self.assertframesequal(result[1]['framegen'], [ + b'bytes-response continuation %s' % first, + b'bytes-response eos %s' % second, + ]) + + def testapplicationerror(self): + reactor = makereactor() + list(sendcommandframes(reactor, b'mycommand', {})) + + result = reactor.onapplicationerror(b'some message') + self.assertaction(result, 'sendframes') + self.assertframesequal(result[1]['framegen'], [ + b'error-response application some message', + ]) + if __name__ == '__main__': import silenttestrunner silenttestrunner.main(__name__)