From: Josh Triplett <josh@joshtriplett.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: upload-pack/ls-remote: showing non-HEAD symbolic refs?
Date: Tue, 16 Aug 2016 15:24:14 -0700 [thread overview]
Message-ID: <20160816222414.GA17195@cloud> (raw)
In-Reply-To: <20160816211551.fjobjxcqvo2dfiry@sigill.intra.peff.net>
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
next prev parent reply other threads:[~2016-08-16 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 16:18 upload-pack/ls-remote: showing non-HEAD symbolic refs? Josh Triplett
2016-08-16 16:31 ` Jeff King
2016-08-16 17:34 ` Josh Triplett
2016-08-16 18:28 ` Jeff King
2016-08-16 18:50 ` Stefan Beller
2016-08-16 20:34 ` Josh Triplett
2016-08-16 20:31 ` Josh Triplett
2016-08-16 20:54 ` Jeff King
2016-08-16 21:11 ` Josh Triplett
2016-08-16 21:15 ` Jeff King
2016-08-16 22:24 ` Josh Triplett [this message]
2016-08-19 13:47 ` Jeff King
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160816222414.GA17195@cloud \
--to=josh@joshtriplett.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.