Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-25 Thread Jeff King
On Tue, May 24, 2016 at 06:46:48PM -0400, David Turner wrote: > I tried to make libcurl do the receive-before-sending thing, but it > doesn't seem to be designed for it (even if you prime things by sending > a "hello" from the client first). My thought was to hook up > CURLOPT_READFUNCTION and

Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-25 Thread David Turner
On Wed, 2016-05-25 at 09:23 -0700, Junio C Hamano wrote: > David Turner 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

Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-25 Thread David Turner
On Wed, 2016-05-25 at 06:03 +0700, Duy Nguyen wrote: > On Wed, May 25, 2016 at 5:46 AM, David Turner < > dtur...@twopensource.com> wrote: > > 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

Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-25 Thread Junio C Hamano
David Turner 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

Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-24 Thread Duy Nguyen
On Wed, May 25, 2016 at 5:46 AM, David Turner wrote: > 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

Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-24 Thread David Turner
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

Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-02 Thread Stefan Beller
On Mon, May 2, 2016 at 1:41 PM, David Turner wrote: > On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote: >> Hi David, >> >> here are my patches for a protocol v2. >> >> ("Negotiate capabilities before doing anything else", or as code: >> >> static void

Re: [WIP PATCH 00/14] Protocol v2 patches

2016-05-02 Thread David Turner
On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote: > Hi David, > > here are my patches for a protocol v2. > > ("Negotiate capabilities before doing anything else", or as code: > > static void upload_pack_version_2(void) > { > send_capabilities_version_2(); >