protocol-capabilities.txt: document no-done
Seemaint3e63b21
(upload-pack: Implement no-done capability - 2011-03-14) and761ecf0
(fetch-pack: Implement no-done capability - 2011-03-14) for more information. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
parent
087e347f26
commit
c9cd60f6fa
|
@ -75,6 +75,18 @@ This is an extension of multi_ack that permits client to better
|
||||||
understand the server's in-memory state. See pack-protocol.txt,
|
understand the server's in-memory state. See pack-protocol.txt,
|
||||||
section "Packfile Negotiation" for more information.
|
section "Packfile Negotiation" for more information.
|
||||||
|
|
||||||
|
no-done
|
||||||
|
-------
|
||||||
|
This capability should only be used with the smart HTTP protocol. If
|
||||||
|
multi_ack_detailed and no-done are both present, then the sender is
|
||||||
|
free to immediately send a pack following its first "ACK obj-id ready"
|
||||||
|
message.
|
||||||
|
|
||||||
|
Without no-done in the smart HTTP protocol, the server session would
|
||||||
|
end and the client has to make another trip to send "done" before
|
||||||
|
the server can send the pack. no-done removes the last round and
|
||||||
|
thus slightly reduces latency.
|
||||||
|
|
||||||
thin-pack
|
thin-pack
|
||||||
---------
|
---------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue