Hi, The creation of a new protocol does not usually make happy to universe (this break-compatibility of proxys, firewall applications, web- servers, etc...) (also I read in another thread an idea "spdy://"), but since it is an HTTP-aware, and it is trying to add optimizations, such as multiplex, persistence and compression by-default,... It would not be better to create HTTP/1.2 and SPEEDY-extension verb?
In the initial handshake in which would create a new verb "STARTSPDY" (like I would make a STARTTLS in a session SMTP or CONNECT ip:port for HTTP) and to initiate an HTTP connection would make a request like: "STARTSPDY xxx HTTP/1.2", followed by the initial negotiation headers spdy and whatever comes after, and being a persistent connection SPDY that requires no more of this overhead, this has the advantage that if the web server does not support this protocol, is compatible with HTTP 1.1. Regards Guillermo -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
