diff tests/test-http-api.t @ 39814: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

--- a/tests/test-http-api.t	Mon Sep 17 11:54:00 2018 -0700
+++ b/tests/test-http-api.t	Thu Sep 20 12:57:23 2018 -0700
@@ -218,11 +218,11 @@
 Accessing a known but not enabled API yields a different error
 
   $ send << EOF
-  > httprequest GET api/exp-http-v2-0001
+  > httprequest GET api/exp-http-v2-0002
   >     user-agent: test
   > EOF
   using raw connection to peer
-  s>     GET /api/exp-http-v2-0001 HTTP/1.1\r\n
+  s>     GET /api/exp-http-v2-0002 HTTP/1.1\r\n
   s>     Accept-Encoding: identity\r\n
   s>     user-agent: test\r\n
   s>     host: $LOCALIP:$HGPORT\r\n (glob)
@@ -234,7 +234,7 @@
   s>     Content-Type: text/plain\r\n
   s>     Content-Length: 33\r\n
   s>     \r\n
-  s>     API exp-http-v2-0001 not enabled\n
+  s>     API exp-http-v2-0002 not enabled\n
 
 Restart server with support for HTTP v2 API
 
@@ -269,7 +269,7 @@
   s>     \r\n
   s>     APIs can be accessed at /api/<name>, where <name> can be one of the following:\n
   s>     \n
-  s>     exp-http-v2-0001
+  s>     exp-http-v2-0002
 
   $ send << EOF
   > httprequest GET api/
@@ -290,4 +290,4 @@
   s>     \r\n
   s>     APIs can be accessed at /api/<name>, where <name> can be one of the following:\n
   s>     \n
-  s>     exp-http-v2-0001
+  s>     exp-http-v2-0002