wireproto: separate commands tables for version 1 and 2 commands We can't easily reuse existing command handlers for version 2 commands because the response types will be different. e.g. many commands return nodes encoded as hex. Our new wire protocol is binary safe, so we'll wish to encode nodes as binary. We /could/ teach each command handler to look at the protocol handler and change behavior based on the version in use. However, this would make logic a bit unwieldy over time and would make it harder to design a unified protocol handler interface. I think it's better to create a clean break between version 1 and version 2 of commands on the server. What I imagine happening is we will have separate @wireprotocommand functions for each protocol generation. Those functions will parse the request, dispatch to a common function to process it, then generate the response in its own, transport-specific manner. This commit establishes a separate table for tracking version 1 commands from version 2 commands. The HTTP server pieces have been updated to use this new table. Most commands are marked as both version 1 and version 2, so there is little practical impact to this change. A side-effect of this change is we now rely on transport registration in wireprototypes.TRANSPORTS and certain properties of the protocol interface. So a test had to be updated to conform. Differential Revision: https://phab.mercurial-scm.org/D2982

     1

http://example.com/no/anchor, branches: (None, [])

     2

http://example.com/an/anchor, branches: ('foo', [])

     3

http://example.com/no/anchor/branches, branches: (None, ['foo'])

     4

http://example.com/an/anchor/branches, branches: ('bar', ['foo'])

     5

http://example.com/an/anchor/branches-None, branches: ('foo', [])

     6

http://example.com/, branches: (None, [])

     7

http://example.com/, branches: (None, [])

     8

http://example.com/, branches: ('foo', [])