From: Nick Hengeveld <nickh@reactrix.com>
To: git@vger.kernel.org
Subject: [RFC] Timeouts on HTTP requests
Date: Tue, 18 Oct 2005 16:51:04 -0700 [thread overview]
Message-ID: <20051018235104.GO5509@reactrix.com> (raw)
Our QA department today checked what would happen if the network connection
went away completely in the middle of an HTTP transfer. It looks as though
the answer is that git-http-fetch sits there forever waiting for CURL to
return something.
I'm thinking of taking advantage of CURL's capability of aborting a request
if the transfer rate drops below a threshold for a specified length of time
using a new pair of environment variables and/or config file settings:
GIT_HTTP_LOW_SPEED_LIMIT/http.lowspeedlimit
GIT_HTTP_LOW_SPEED_TIME/http.lowspeedtime
Does this make sense, and if so should there be defaults if nothing is
specified?
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next reply other threads:[~2005-10-18 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 23:51 Nick Hengeveld [this message]
2005-10-19 6:02 ` [RFC] Timeouts on HTTP requests Junio C Hamano
2005-10-19 11:09 ` Petr Baudis
2005-10-19 15:34 ` Nick Hengeveld
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=20051018235104.GO5509@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).