On Sat, Jul 11, 2015 at 11:26 AM, Ilari Liusvaara <ilari.liusvaara@xxxxxxxxxxx> wrote: > On Sat, Jul 11, 2015 at 10:23:09AM -0700, Shawn Pearce wrote: >> >> > Websockets over HTTP/2 (a.k.a. "websockets2") has not been defined yet. >> > With Websockets(1), it would probably already be possible to tunnel the >> > native git smart transport protocol over it. Probably not worth it. >> >> Another option is to tunnel using gRPC (grpc.io). libcurl probably >> can't do this. And linking grpc.io library into git-core is crazy. So >> its probably a non-starter. But food for thought. > > Wouldn't it link into git-remote-http (and on the server side, one > could use pipes to talk to git)? > > But supporting websockets in git-remote-http could get annoying, > especially for wss:// (https://). Dunno how bad gRPC would be. We wrote it as git-remote-$THING, invoked with $THING:// URLs. And git-remote-$THING just implements the "connect" helper protocol. Its much simpiler than git-remote-http. Maybe its done that way in git-core as http2:// aka git-remote-http2. Or the git-remote-http helper connects to the remote system and tries to guess if it supports Git on HTTP/2 before responding to the capabilities request from transport code. If yes, it replies with connect, if no, it does the current fetch and push protocol. -- 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