From: Nick Hengeveld <nickh@reactrix.com>
To: git@vger.kernel.org
Subject: [PATCH 0/5] HTTP refactoring/cleanup
Date: Fri, 18 Nov 2005 11:02:52 -0800 [thread overview]
Message-ID: <20051118190251.GE3968@reactrix.com> (raw)
The following set of patches cleans up http-fetch and http-push.
- Common HTTP code has been moved to http.c/http.h. While
curl-specific code still exists in both http-fetch and http-push,
it is a step in the direction of allowing use of a different HTTP
request library if someone is so inclined.
- Object request functions and data have been renamed to keep clear
what types of requests are being processed, which will make it
easier to process additional types of requests in parallel (eg.
starting pack downloads immediately when an object 404s)
- The reliability and performance of http-fetch has been improved when
built in an environment without curl multi support.
- XML parsing in http-push has been improved, which will make it
easier to add functionality to update remote server info.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
reply other threads:[~2005-11-18 19:03 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=20051118190251.GE3968@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).