On Wed, 2016-05-25 at 09:23 -0700, Junio C Hamano wrote: > David Turner <dturner@xxxxxxxxxxxxxxxx> writes: > > > I was looking at this again today, and noticed that it doesn't > > really > > address the HTTP case. > > > > The central problem is that protocol v2 goes like this: > > server: I have capabilities w,x,y, and z > > client: I want capabilities x and z. > > > > But HTTP goes like this: > > client: [request] > > server: [response] > > I wonder if that can be solved by speculative request? > > Let the connection initiator say "If you can do x and z, please do > so", and allow the responder to say either "OK, I can do x and z; by > the way the full capabilites I support are w, x, y and z", or > "Sorry, can't do that; I have capabilities w, x, and y". That protocol is somewhat more complicated. And it's different than the v2 protocol for the other transports (unless you are thinking that we should change those too?). It's actually a tiny bit like what I originally proposed for HTTP. It sounds OK to me, but I want to know what others think before I start implementing. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html