##// END OF EJS Templates
wireprotov2: allow multiple fields to follow revision maps...
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

File last commit:

r38475:11eda1f1 default
r39839:d059cb66 default
Show More
fedora21
15 lines | 263 B | text/plain | TextLexer
Gregory Szorc
packaging: move most of contrib/docker to contrib/packaging/docker...
r38023 FROM fedora:21
Gregory Szorc
packaging: consistently create build user in Dockerfiles...
r38475
RUN groupadd -g 1000 build && \
useradd -u 1000 -g 1000 -s /bin/bash -d /build -m build
Gregory Szorc
packaging: move most of contrib/docker to contrib/packaging/docker...
r38023 RUN yum install -y \
gcc \
gettext \
make \
python-devel \
python-docutils \
rpm-build
# For creating repo meta data
RUN yum install -y createrepo