From: Nick Hengeveld <nickh@reactrix.com>
To: git@vger.kernel.org
Subject: [PATCH 0/4] git-http-push improvements
Date: Fri, 4 Nov 2005 14:22:10 -0800 [thread overview]
Message-ID: <20051104222210.GC3001@reactrix.com> (raw)
This series of patches makes HTTP/DAV pushes more stable. Locks are
handled much better and are refreshed if they are about to expire, and
remote refs with '/' in their names are supported.
Items still on my todo list:
- Process the server's lock refresh timeout response (currently it
assumes that the original lock timeout will continue to work.)
- Verify remote commit object if branches are the same (currently
it does no verification if the refs point to the same object.)
- Clean up temp filenames after failed PUTs (no need to leave them
there since you can't resume.)
- Either send compressed objects directly rather than uncompressing and
recompressing them before sending; or since we have an uncompressed
copy, also verify the SHA1 before sending since the remote doesn't
verify (and/or consider read after write verification.)
- Use a pack to send under what circumstances? Perhaps allow
min-pack-size and max-pack-size (more objects == less impact on failed
transfer, more transfer overhead.)
- Attempt recovery if the remote ref PUT fails?
- Test against other DAV servers (I've currently tested it using only
Apache.)
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
reply other threads:[~2005-11-04 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051104222210.GC3001@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.