From: Shawn Pearce <email@example.com>
To: Ilari Liusvaara <firstname.lastname@example.org>
Cc: ForceCharlie <email@example.com>, git <firstname.lastname@example.org>
Subject: Re: Git Smart HTTP with HTTP/2.0
Date: Sat, 11 Jul 2015 16:10:06 -0700 [thread overview]
Message-ID: <CAJo=hJuM70o8+U3Wt3rRzyrB1O=Q+wz3bGZVFa07zRQ0Ughk9g@mail.gmail.com> (raw)
On Sat, Jul 11, 2015 at 11:26 AM, Ilari Liusvaara
> 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.
prev parent reply other threads:[~2015-07-11 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 3:10 Git Smart HTTP with HTTP/2.0 ForceCharlie
2015-07-11 7:00 ` Ilari Liusvaara
2015-07-11 17:23 ` Shawn Pearce
2015-07-11 18:26 ` Ilari Liusvaara
2015-07-11 23:10 ` Shawn Pearce [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).