Jonathan Tan <jonathantanmy@xxxxxxxxxx> writes: >> For a real implementation, I think we'd want to do the negotiation >> inside the conversation between send-pack and receive-pack, so that >> what is agreed to be common between two parties will not shift in >> the middle (in the same spirit that upload-pack grabs all the >> relevant refs first, advertises them, negotiates what is common and >> creates a pack, all using the same worldview of where the tips of >> refs are throughout the process, even if some refs change in the >> meantime). > > Upload-pack does that for protocol v0 ssh:// and git:// but not > http(s)://, and does not do that for protocol v2, I believe. > > If we were to do that, I don't think it would work for the transports > that have are stateless (e.g. HTTP). Yeah, I consider it a bug in the "stateless" hack, though, and v2 somehow chose to take the common denominator to propagate the same bug to protocols that are otherwise capable of being stateful. In any case, I think I heard in another response from you that you plan to do only v2, and I think that is OK. Perhaps we can have a separate service (like 'ls-refs' is a service that can be used independent of the 'fetch' service in v2, and can be used by somebody trying to 'push') 'negotiate' that can become a separate thing, so that "fetch<->upload-pack" conversation would become ls-refs plus negotiate plus fetch, while "push<->receive-pack" conversation would become ls-refs plus negotiate plus push? Thanks.
