diff mercurial/wireproto.py @ 36613:6e585bca962e

wireproto: add transport specific capabilities in the transport

We add a method to the protocol handler interface that allows
specific implementations to add their own capabilities.

The SSH implementation is a no-op.

The HTTP implementation adds the HTTP-specific capabilities.

The end result is transport specific capabilities now live in the
transport code instead of in some generic function in the wireproto
module.

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

--- a/mercurial/wireproto.py	Tue Feb 27 15:23:04 2018 -0800
+++ b/mercurial/wireproto.py	Tue Feb 27 16:24:02 2018 -0800
@@ -819,23 +819,7 @@
         caps.append('bundle2=' + urlreq.quote(capsblob))
     caps.append('unbundle=%s' % ','.join(bundle2.bundlepriority))
 
-    if proto.name == 'http-v1':
-        caps.append('httpheader=%d' %
-                    repo.ui.configint('server', 'maxhttpheaderlen'))
-        if repo.ui.configbool('experimental', 'httppostargs'):
-            caps.append('httppostargs')
-
-        # FUTURE advertise 0.2rx once support is implemented
-        # FUTURE advertise minrx and mintx after consulting config option
-        caps.append('httpmediatype=0.1rx,0.1tx,0.2tx')
-
-        compengines = supportedcompengines(repo.ui, util.SERVERROLE)
-        if compengines:
-            comptypes = ','.join(urlreq.quote(e.wireprotosupport().name)
-                                 for e in compengines)
-            caps.append('compression=%s' % comptypes)
-
-    return caps
+    return proto.addcapabilities(repo, caps)
 
 # If you are writing an extension and consider wrapping this function. Wrap
 # `_capabilities` instead.