Re: Git Smart HTTP with HTTP/2.0

2015-07-11 Thread Shawn Pearce
On Sat, Jul 11, 2015 at 11:26 AM, Ilari Liusvaara wrote: > On Sat, Jul 11, 2015 at 10:23:09AM -0700, Shawn Pearce wrote: >> >> > Websockets over HTTP/2 (a.k.a. "websockets2") has not been defined yet. >> > With Websockets(1), it would probably already be possible to tunnel the >> > native git smar

Re: Git Smart HTTP with HTTP/2.0

2015-07-11 Thread Ilari Liusvaara
On Sat, Jul 11, 2015 at 10:23:09AM -0700, Shawn Pearce wrote: > On Sat, Jul 11, 2015 at 12:00 AM, Ilari Liusvaara > wrote: > > On Sat, Jul 11, 2015 at 11:10:48AM +0800, ForceCharlie wrote: > > > >> Frequently used Git developers often feel Git HTTP protocol is not > >> satisfactory, slow and unsta

Re: Git Smart HTTP with HTTP/2.0

2015-07-11 Thread Shawn Pearce
On Sat, Jul 11, 2015 at 12:00 AM, Ilari Liusvaara wrote: > On Sat, Jul 11, 2015 at 11:10:48AM +0800, ForceCharlie wrote: >> As we known, HTTP/2.0 has been released. All Git-Smart-HTTP are currently >> implemented using HTTP/1.1. > > Nit: It is HTTP/2. > >> Frequently used Git developers often feel

Re: Git Smart HTTP with HTTP/2.0

2015-07-11 Thread Ilari Liusvaara
On Sat, Jul 11, 2015 at 11:10:48AM +0800, ForceCharlie wrote: > As we known, HTTP/2.0 has been released. All Git-Smart-HTTP are currently > implemented using HTTP/1.1. Nit: It is HTTP/2. > Frequently used Git developers often feel Git HTTP protocol is not > satisfactory, slow and unstable.This i

Git Smart HTTP with HTTP/2.0

2015-07-10 Thread ForceCharlie
As we known, HTTP/2.0 has been released. All Git-Smart-HTTP are currently implemented using HTTP/1.1. Frequently used Git developers often feel Git HTTP protocol is not satisfactory, slow and unstable.This is because the HTTP protocol itself decides When HTTP/2.0 is published. We might be able to