path: root/fetch-pack.h
diff options
authorShawn O. Pearce <>2009-10-31 00:47:41 (GMT)
committerJunio C Hamano <>2009-11-05 01:58:15 (GMT)
commitde1a2fdd38b138c4e4fed6412783dcb74d63d2da (patch)
tree9aa2f8b91e1106c23644481b6aadee11b3386ae7 /fetch-pack.h
parent97cc7bc45c2e076184b84749952b216036a6ecd6 (diff)
Smart push over HTTP: client side
The git-remote-curl backend detects if the remote server supports the git-receive-pack service, and if so, runs git-send-pack in a pipe to dump the command and pack data as a single POST request. The advertisements from the server that were obtained during the discovery are passed into git-send-pack before the POST request starts. This permits git-send-pack to operate largely unmodified. For smaller packs (those under 1 MiB) a HTTP/1.0 POST with a Content-Length is used, permitting interaction with any server. The 1 MiB limit is arbitrary, but is sufficent to fit most deltas created by human authors against text sources with the occasional small binary file (e.g. few KiB icon image). The configuration option http.postBuffer can be used to increase (or shink) this buffer if the default is not sufficient. For larger packs which cannot be spooled entirely into the helper's memory space (due to http.postBuffer being too small), the POST request requires HTTP/1.1 and sets "Transfer-Encoding: chunked". This permits the client to upload an unknown amount of data in one HTTP transaction without needing to pregenerate the entire pack file locally. Signed-off-by: Shawn O. Pearce <> CC: Daniel Barkalow <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'fetch-pack.h')
0 files changed, 0 insertions, 0 deletions