On Tue, Aug 16, 2016 at 05:15:51PM -0400, Jeff King wrote: > On Tue, Aug 16, 2016 at 02:11:41PM -0700, Josh Triplett wrote: > > > > For HTTPS, I'd just as soon use HTTP-level features. > > > > ALPN, used carefully, could potentially allow eliminating one round-trip > > compared to HTTPS, and could also allow full-duplex communication. > > I'd love to have a real full-duplex git-over-https. I looked into > WebSockets at one point, but it looked non-trivial and I gave up. WebSockets would be non-trivial, and require server configuration as well, but it could work. > But if we had a real full-duplex connection over https, I think there > would be no reason for git:// to continue existing (we'd probably keep > ssh as it's a useful protocol for authentication, though). Agreed. Using ALPN wouldn't actually end up using HTTPS; it would negotiate with the server and end up connected directly to a git program speaking an arbitrary protocol over TLS. Many web servers already support ALPN to negotiate HTTP/2, so this seems plausible. Another alternative would be to define a framing for a full-duplex git-upload-pack connection inside a single HTTP/2 connection; HTTP/2 already effectively allows full-duplex asynchronous conversations. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html