From: Jonathan Nieder <jrnieder@gmail.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: http-protocol question
Date: Mon, 1 Dec 2014 20:45:22 -0800 [thread overview]
Message-ID: <20141202044522.GZ6527@google.com> (raw)
In-Reply-To: <CAGyf7-GZbRBN4O_yNgrmJCya=6f8XQ4O8m7WBa1k8Ve196ajYQ@mail.gmail.com>
Hi,
Bryan Turner wrote:
> The reason I ask is that there is a race condition that exists where
> the ref advertisement lists refs/heads/foo at abc1234, and then foo is
> deleted before the actual upload-pack request comes in.
Can you say more about the context? For example, was this actually
happening, or is this for the sake of understanding the protocol
better?
I ask because knowing the context might help us give more specific
advice.
Sometimes when people delete a branch they really want those objects
to be inaccessible *right away*. So for such people, git's behavior
of failing the request unless the objects are still accessible by
some other path is helpful.
A stateful server could theoretically cache the list of objects they
have advertised for a short time, to avoid clients having to suffer
when something becomes inaccessible during the window between the
upload-pack advertisement and upload-pack request. Or a permissive
server can allow all wants except a specific blacklist (and some
people do that).
Jonathan
next prev parent reply other threads:[~2014-12-02 4:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 2:17 http-protocol question Bryan Turner
2014-12-02 3:34 ` Jonathan Nieder
2014-12-02 4:28 ` Bryan Turner
2014-12-02 4:29 ` Bryan Turner
2014-12-02 4:45 ` Jonathan Nieder [this message]
2014-12-02 5:04 ` Bryan Turner
2014-12-02 5:17 ` Jonathan Nieder
2014-12-02 5:30 ` Duy Nguyen
2014-12-02 5:37 ` Duy Nguyen
2014-12-02 5:33 ` Jeff King
2014-12-02 5:47 ` Bryan Turner
2014-12-02 5:52 ` Jeff King
2014-12-02 17:45 ` Junio C Hamano
2014-12-02 19:50 ` 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=20141202044522.GZ6527@google.com \
--to=jrnieder@gmail.com \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).