On Monday 12 November 2012 02:57:25 Aribe Hernandez wrote:
[...]
> Back in August there was some talk on the spdy-dev Google Group about
> when to EOL SPDY/2 and it was suggested that Google would drop SPDY/2
> from Chrome 23 in early November. Chrome 23 has since been released
> and fortunately it still supports SPDY/2.
> https://groups.google.com/forum/#!msg/spdy-dev/zvA6Ohqs9Ew/8kkBLYMniQoJ
> https://groups.google.com/forum/?fromgroups=#!topic/spdy-dev/A0sCEnZBEcs

Don't worry. If you read carefully the discussion referenced by the last link,
you will find that "End-of-Life for SPDY/2" postponed to SPDY/4 plus some time.

> The SPDY/3 spec was published as an IETF draft in February, 2012 and
> since then support for SPDY/3 has shown up in major browsers (July,
> 2012). Among non-browser software, Jetty (Java app server), HAproxy
> (load balancing proxy) and the mod_spdy module for Apache all features
> support for SPDY/3.

Yes. And SPDY/3 has no noticeable improvements compared to SPDY/2, but
instead it has some problems. See:

http://japhr.blogspot.ru/2012/05/spdy3-flow-control-comparisons.html
https://groups.google.com/d/msg/spdy-dev/JB_aQPNI7rw/10UFCLfeCxgJ

> Work is currently underway on developing the next iteration of the spec,
> SPDY/4.
>
> Nginx is worryingly missing from the list of software supporting
> SPDY/3 (as well as general SPDY discussions). Was the SPDY/2 thing for
> Nginx just a one shot thing or are there actual plans for the future
> of SPDY in Nginx?

The current plan is to integrate spdy implementation into the nginx code base as
painless as possible in terms of code reuse and follow-up support.

Work is going on, but that is not related to the patch.

wbr, Valentin V. Bartenev

--
http://nginx.com/support.html
http://nginx.org/en/donation.html

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx