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 is because the HTTP protocol itself > decides Note that there are already two versions of HTTP transport, the old "dumb" one and the newer "smart" one. The smart one is difficult to speed up (due to nature of the negotiations), but usually is pretty reliable (the efficiency isn't horrible). Now, the old "dumb" protocol is pretty unreliable and slow. HTTP/2 probably can't do anything with the reliability problems, but probably could improve the speed a bit. 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 smart transport protocol over it. Probably not worth it. > When HTTP/2.0 is published. We might be able to git developers jointly, > based on HTTP/2.0 Git-Smart-HTTP service and client support. > HTTP/2.0: https://tools.ietf.org/html/rfc7540 Well, it is published already. -Ilari -- 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