From: Nick Hengeveld <nickh@reactrix.com>
To: git@vger.kernel.org
Subject: HTTP pushes
Date: Mon, 31 Oct 2005 18:02:48 -0800 [thread overview]
Message-ID: <20051101020248.GA3928@reactrix.com> (raw)
HTTP is currently listed as a read-only/unsupported method for doing
pushes, is that due to inherent problems with HTTP or just because
it hasn't been written yet?
I've built a working prototype of an HTTP push implementation using DAV.
It locks the remote branch file during the push and PUTs to temp files to
insure nobody else reads objects while they're being pushed. It does
not validate remote objects - if they exist on the remote end as loose
objects or in a pack, local copies won't be pushed. It supports sparse
object directories, and verifies that the remote branch is an ancestor
of the local branch before doing anything.
I'm curious to know whether it would be useful to proceed further, and
to know what I haven't thought about yet...
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next reply other threads:[~2005-11-01 2:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 2:02 Nick Hengeveld [this message]
2005-11-01 19:10 ` HTTP pushes Johannes Schindelin
2005-11-02 0:36 ` Junio C Hamano
2005-11-02 0:46 ` David Lang
2005-11-02 0:59 ` Nick Hengeveld
2005-11-02 1:10 ` Johannes Schindelin
2005-11-01 20:06 ` Daniel Barkalow
2005-11-03 4:12 ` H. Peter Anvin
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=20051101020248.GA3928@reactrix.com \
--to=nickh@reactrix.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).