Mercurial > public > mercurial-scm > hg-stable
diff tests/test-wireproto-command-listkeys.t @ 39819:d059cb669632
wireprotov2: allow multiple fields to follow revision maps
The *data wire protocol commands emit a series of CBOR values.
Because revision/delta data may be large, their data is emitted
outside the map as a top-level bytestring value.
Before this commit, we'd emit a single optional bytestring
value after the revision descriptor map. This got the job done.
But it was limiting in that we could only send a single field.
And, it required the consumer to know that the presence of a
key in the map implied the existence of a following bytestring
value.
This commit changes the encoding strategy so top-level bytestring
values in the stream are explicitly denoted in a "fieldsfollowing"
key. This key contains an array defining what fields that follow
and the expected size of each field.
By defining things this way, we can easily send N bytestring
values without any ambiguity about their order. In addition,
clients only need to know how to parse ``fieldsfollowing`` to
know if extra values are present.
Because this breaks backwards compatibility, we've bumped the version
number of the wire protocol version 2 API endpoint.
Differential Revision: https://phab.mercurial-scm.org/D4620
| author | Gregory Szorc <gregory.szorc@gmail.com> |
|---|---|
| date | Thu, 20 Sep 2018 12:57:23 -0700 |
| parents | 07b58266bce3 |
| children | 393e44324037 |
line wrap: on
line diff
--- a/tests/test-wireproto-command-listkeys.t Mon Sep 17 11:54:00 2018 -0700 +++ b/tests/test-wireproto-command-listkeys.t Thu Sep 20 12:57:23 2018 -0700 @@ -31,7 +31,7 @@ > EOF creating http peer for wire protocol version 2 sending listkeys command - s> POST /api/exp-http-v2-0001/ro/listkeys HTTP/1.1\r\n + s> POST /api/exp-http-v2-0002/ro/listkeys HTTP/1.1\r\n s> Accept-Encoding: identity\r\n s> accept: application/mercurial-exp-framing-0005\r\n s> content-type: application/mercurial-exp-framing-0005\r\n @@ -77,7 +77,7 @@ > EOF creating http peer for wire protocol version 2 sending listkeys command - s> POST /api/exp-http-v2-0001/ro/listkeys HTTP/1.1\r\n + s> POST /api/exp-http-v2-0002/ro/listkeys HTTP/1.1\r\n s> Accept-Encoding: identity\r\n s> accept: application/mercurial-exp-framing-0005\r\n s> content-type: application/mercurial-exp-framing-0005\r\n @@ -122,7 +122,7 @@ > EOF creating http peer for wire protocol version 2 sending listkeys command - s> POST /api/exp-http-v2-0001/ro/listkeys HTTP/1.1\r\n + s> POST /api/exp-http-v2-0002/ro/listkeys HTTP/1.1\r\n s> Accept-Encoding: identity\r\n s> accept: application/mercurial-exp-framing-0005\r\n s> content-type: application/mercurial-exp-framing-0005\r\n