From: Jonathan Tan <jonathantanmy@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
markbt@efaref.net, git@jeffhostetler.com
Subject: Re: Proposal for "fetch-any-blob Git protocol" and server design
Date: Thu, 16 Mar 2017 15:48:19 -0700 [thread overview]
Message-ID: <3c89fee5-2226-6760-f2fd-222432230612@google.com> (raw)
In-Reply-To: <xmqq7f3oc45v.fsf@gitster.mtv.corp.google.com>
On 03/16/2017 02:17 PM, Junio C Hamano wrote:
> Yeah, the example was solely to see how the system was to be
> extended, as one of the selling point of the proposal was:
>
> > === Endpoint support for forward compatibility
> >
> > This "server" endpoint requires that the first line be understood, but
> > will ignore any other lines starting with words that it does not
> > understand. This allows new "commands" to be added (distinguished by
> > their first lines) and existing commands to be "upgraded" with
> > backwards compatibility.
<snip>
>
> And the lack of "capability negotiation" is substituted by "assume
> the better server, fallback to lower common denominator by detecting
> errors"?
Yes. I probably should have mentioned that this "forward compatibility"
is limited - it does not include any potential new feature intending to
reduce the size of the request. I was thinking more of this being able
to be extended to, for example, add "hint" lines that certain blobs come
from certain commits, or add "have" lines to present blobs that might be
good delta bases (and even if the server doesn't understand these lines,
its output is still correct).
next prev parent reply other threads:[~2017-03-16 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 22:57 Proposal for "fetch-any-blob Git protocol" and server design Jonathan Tan
2017-03-15 17:59 ` Junio C Hamano
2017-03-16 17:31 ` Jonathan Tan
2017-03-16 21:17 ` Junio C Hamano
2017-03-16 22:48 ` Jonathan Tan [this message]
2017-03-28 23:19 ` Stefan Beller
[not found] ` <00bf01d2aed7$b13492a0$139db7e0$@gmail.com>
2017-04-12 22:02 ` Kevin David
2017-04-13 20:12 ` Jonathan Tan
2017-04-21 16:41 ` Kevin David
2017-04-26 22:51 ` Jonathan Tan
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
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 \
--in-reply-to=3c89fee5-2226-6760-f2fd-222432230612@google.com \
--to=jonathantanmy@google.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=markbt@efaref.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).