Re: [PATCH v2] Add persistent-https to contrib

Colby Ranger [off-list ref] writes:

Git over HTTPS has a high request startup latency, since the SSL
negotiation can take up to a second. In order to reduce this latency,
connections should be left open to the Git server across requests
(or invocations of the git commandline).

Reduce SSL startup latency by running a daemon job that keeps
connections open to a Git server. The daemon job
(git-remote-persistent-https--proxy) is started on the first request
through the client binary (git-remote-persistent-https) and remains
running for 24 hours after the last request, or until a new daemon
binary is placed in the PATH. The client determines the daemon's
HTTP address by communicating over a UNIX socket with the daemon.
From there, the rest of the Git protocol work is delegated to the
"git-remote-http" binary, with the environment's http_proxy set to
the daemon.

Signed-off-by: Colby Ranger <redacted>
---

Thanks.  I'll add a few paragraphs taken from Shawn's message in
this thread before queuing, but it'll take some time until I get to
this patch (I am looking at a totally unrelated topic that brought an
unpleasant regression to cherry-pick).