comparison mercurial/configitems.py @ 37558:8a73132214a3

httppeer: support protocol upgrade

With the new handshake defined and in place on the server, we can
now implement it on the client.

The HTTP handshake mechanism has been taught to add headers advertising
its support for the new capabilities response. Response handling
has been adjusted to allow CBOR responses through. And makepeer()
has been taught to instantiate a mutually supported peer.

The HTTPv2 peer class doesn't implement the full peer interface. So
HTTPv2 is not yet usable as a peer.

Like the server side, we support registering handlers for
different API services. This allows extensions to easily implement
API services and peers. A practical use case for this is to
provide a previous implementation of the experimental version 2
wire protocol to a future version of Mercurial. We know there will
be BC breaks after 4.6 ships. But someone could take the peer and
server code from 4.6, drop it in an extension, and allow its use
indefinitely.

Differential Revision: https://phab.mercurial-scm.org/D3243

37557:734515aca84d

    default=dynamicdefault,
)
coreconfigitem('experimental', 'hook-track-tags',
    default=False,
)
coreconfigitem('experimental', 'httppostargs',
    default=False,
)
coreconfigitem('experimental', 'mergedriver',
    default=None,

37558:8a73132214a3

    default=dynamicdefault,
)
coreconfigitem('experimental', 'hook-track-tags',
    default=False,
)
coreconfigitem('experimental', 'httppeer.advertise-v2',
    default=False,
)
coreconfigitem('experimental', 'httppostargs',
    default=False,
)
coreconfigitem('experimental', 'mergedriver',
    default=None,