Re: Git-aware HTTP transport
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- Aug 28, 2008, 17:26 UTC
- Message-ID
- <20080828172623.GD21072@spearce.org>
- In-Reply-To
- <48B6DE7A.1020207@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> wrote:
Show 16 quoted lines
> Shawn O. Pearce wrote: >> "H. Peter Anvin" <hpa@zytor.com> wrote: >>> >>> I *think* the "native" git protocol uses binary here. It makes sense >>> to be consistent, to allow them to share code? >> >> No, the native protocol is horribly verbose here: >> >> 0032want ac3abe10ed54d512fbbaeb7cef19972eedd8e4a8 >> ... >> >> so its doing it in hex, and its using 10 bytes of "framing" for >> every SHA-1 it sends as each is sent in its own pkt-line with the >> have/want header. > > Hm. It's probably not enough data to worry significantly about.
Should I change the HTTP protocol then to use the same format, so they have a better chance at sharing code between them?
-- Shawn.