W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: HTTP/2.0 draft, NPN/ALPN, and TLS

From: Patrick McManus <mcmanus@ducksong.com>
Date: Tue, 10 Dec 2013 08:01:37 -0500
Message-ID: <CAOdDvNppZKBz8iE48Wg-T2Z+fqZ4YWt317Je_sZthEuseXLp_w@mail.gmail.com>
To: Chris Burdess <dog@gnu.org>
Cc: Daniel Stenberg <daniel@haxx.se>, HTTP Working Group <ietf-http-wg@w3.org>
On Tue, Dec 10, 2013 at 2:58 AM, Chris Burdess <dog@gnu.org> wrote:

> SPDY deployment is basically 100% Google.


 that's not right.

. spdy is in (listed in order of appearance) chrome, firefox, opera, and
ie. Its supported on the server side at google, twitter, facebook,
wordpress, in nginx, as an apache module, and by at least one cdn. Its in
F5 Big IP and (I think) the citrix load balancer product too. sdpy has been
shown to work and the engineers who have done that work have gotten
together in this forum to create an open specification for it.

I think an ipsec multiplexed web browser would be awesome - I encourage you
to go build one, measure it, find as many other people interested in
standardization and bring the results here. I'd be very interested in that
work.
Received on Tuesday, 10 December 2013 13:02:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:20 UTC