| commit | 8c836c6f21a07897faae41c6132ba49e66025328 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 6 Jan 2010 18:21:05 +0000 (6 10:21 -0800) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 12 Jan 2010 20:01:28 +0000 (12 12:01 -0800) | ||
| tree | b3de30c12ebf492af3516c9f1df6d4bea123a72c | treesnapshot (tar.gz zip) |
| parent | 2e5214462e7f7d93ff39b522c2343105443393c9 | commitdiff |
client side smart HTTP
During fetch over http:// clients now try to take advantage of
the info/refs?service=git-upload-pack URL to determine if the
remote side will support a standard upload-pack command stream.
If so each block of 32 have lines is sent in one POST request,
prefixed by all of the 'want' lines and any previously discovered
common bases as 'have' lines.
During push over http:// clients now try to take advantage of
the info/refs?service=git-receive-pack URL to determine if the
remote side will support a standard receive-pack command stream.
If so, commands are sent along with their pack in a single HTTP
POST request.
Bug: 291002
Change-Id: I8c69b16ac15c442e1a4c3bd60b4ea1a47882b851
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
During fetch over http:// clients now try to take advantage of
the info/refs?service=git-upload-pack URL to determine if the
remote side will support a standard upload-pack command stream.
If so each block of 32 have lines is sent in one POST request,
prefixed by all of the 'want' lines and any previously discovered
common bases as 'have' lines.
During push over http:// clients now try to take advantage of
the info/refs?service=git-receive-pack URL to determine if the
remote side will support a standard receive-pack command stream.
If so, commands are sent along with their pack in a single HTTP
POST request.
Bug: 291002
Change-Id: I8c69b16ac15c442e1a4c3bd60b4ea1a47882b851
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>