Google has announced giving up SPDY after HTTP/2.0 has integrated the protocol and its standardization is in its final stages.
The idea behind Proxygen is not to replace Apache but having the ability to create a specialized high-performance web server that can be embedded into existing applications providing web services. Facebook initially started to build a proxy (hence the name) server in 2011, and now they are open sourcing it after the project evolved and has been tested in production for a number of years.
QUIC (Quick UDP Internet Connections, pronounced 'quick') is a multiplexing transport protocol running over UDP with the main goal to have 0-RTT connectivity overhead.
Twitter has developed and open sourced CocoaSPDY, a framework for OS X (Cocoa) and iOS (Cocoa Touch) based on the implementation they previously contributed to Netty, updating in the same time their iOS application to use SPDY instead of plain HTTP. Twitter has noticed up to 30% decrease in communication latency, the improvement being more noticeable when an “user’s network conditions get worse.“
The editors of the HTTP specification have published an initial draft of v2 which is a straight copy of SPDY and will be used as a base for diffs going forward. Many changes are expected to be done like adding new features, removing existing ones, changing the bytes on the wire, etc. A draft ready for test implementations is expected to be published early next year.
IETF has discussed the future of HTTP, and the next version is to be using SPDY as a starting point. There is a controversy though: Microsoft claims SPDY is no better than HTTP/1.1 with all optimizations turned on, while SPDY’s inventor says Microsoft’s tests actually confirm SPDY’s advantage in a real world scenario.
Lori MacVittie has recently posted an article describing why she believes SPDY will gain much wider acceptance in the Web than WebSockets. For her and several others, the differentiating aspect between these protocols is the way in which they use HTTP and SPDY wins because of this.
Google and Microsoft want to improve HTTP with SPDY and Speed+Mobility. This article reviews both proposals outlining what benefits they bring to the much used Internet protocol.
Rackspace's Mark Nottingham, discusses the recent HTTPbis Working Group meeting, clarifications to the HTTP/1.1 specification, and the influence of SPDY on the group that have resulted in a change to its charter enabling them to begin considering HTTP/2.0.
The Netty 3.3.1 release adds support for SPDY protocol, which has been proposed for inclusion in http/2.0, fixes regression of Android support and reduces memory consumption of ZLib compression.