git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Smart HTTP with HTTP/2.0

From
ILIlari Liusvaara <ilari.liusvaara@elisanet.fi>
Date
Jul 11, 2015, 07:00 UTC
Message-ID
<20150711070055.GA4061@LK-Perkele-VII>
In-Reply-To
<BLU403-EAS33258611CF3B5B553B1C996A09E0@phx.gbl>
On Sat, Jul 11, 2015 at 11:10:48AM +0800, ForceCharlie wrote:
> As we known, HTTP/2.0 has been released. All Git-Smart-HTTP are currently
> implemented using HTTP/1.1.
Nit: It is HTTP/2.
 
> Frequently used Git developers often feel Git HTTP protocol is not
> satisfactory, slow and unstable.This is because the HTTP protocol itself
> decides

Note that there are already two versions of HTTP transport, the old "dumb" one and the newer "smart" one.

The smart one is difficult to speed up (due to nature of the negotiations), but usually is pretty reliable (the efficiency isn't horrible).

Now, the old "dumb" protocol is pretty unreliable and slow. HTTP/2 probably can't do anything with the reliability problems, but probably could improve the speed a bit.

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.

> When HTTP/2.0 is published. We might be able to git developers jointly,
> based on HTTP/2.0 Git-Smart-HTTP service and client support.
> HTTP/2.0: https://tools.ietf.org/html/rfc7540
Well, it is published already.
 
-Ilari
Previous: ForceCharlieNext: Shawn Pearce
Message 2 of 5 in “Git Smart HTTP with HTTP/2.0”
  1. ForceCharlieJul 11, 2015
  2. Ilari LiusvaaraJul 11, 2015
  3. Shawn PearceJul 11, 2015
  4. Ilari LiusvaaraJul 11, 2015
  5. Shawn PearceJul 11, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.