6 ms·
Go language's HTTP/2 demo and interop server
- alexandern 12y agoNice to see more and more implementations popping up. You can track the development of HTTP/2 servers and clients over at https://github.com/http2/http2-spec/wiki/Implementations https://github.com/http2/http2-spec/wiki/Implementations.
- drsintoma 12y agowhat are the main differences between SPDY 4 and 3.1?
- latch 12y agoThis recent post and accompanying comments might help: https://news.ycombinator.com/item?id=8549348 https://news.ycombinator.com/item?id=8549348
- nnx 12y agoPretty awesome. Does this library also support backward compat with SPDY 3.x? (which isn't yet in the standard lib either)
- nnx 12y agoJust checked, nope. TLS NPN does not advertise SPDY 3.x support.
- htor 12y agoExciting to see this standard being built and also very useful to see the performance comparisons with HTTP/1 communication. I wonder if HTTP/2 will change the way we develop websites now that it's cheaper to load resources?
- dariopy 12y agoStop pretending Go is going to happen. It won't. Neither will Dart, btw.
- elmin 12y agoI write it every day. It's happening for me.
- hahainternet 12y agoI uh, don't think you know what you're talking about. I have production Go code running right now.
- SEJeff 12y agoThe 3rd biggest web host, Digital Ocean seems to be a fan! https://twitter.com/digitalocean/status/460844653424541696 https://twitter.com/digitalocean/status/460844653424541696
- placeybordeaux 12y agoThat tweet seems to be about go, not SPDY
- biomechanica 12y agoDocker seems pretty useful. CoreOS seems pretty useful, too. Hmm.. Yeah, Go definitely isn't going to happen. /s
- hobarrera 12y agoSo, go fails to work on IPv6 environments, but they've gone through the effort to actually implement http2? Looks like their priorities are all messed up. :-/
- chimeracoder 12y agoWhat are you talking about? The net package does support ipv6[0]. Also, while ipv6 is important, let's keep in mind that many hosting providers (including Amazon) still don't provide IPv6, and have no timeline for it either. HTTP2 is at the application level, so it is useful immediately, without any change to existing infrastructure. [0] http://golang.org/pkg/net/ http://golang.org/pkg/net/
- hobarrera 12y ago> Also, while ipv6 is important, let's keep in mind that many hosting providers (including Amazon) still don't provide IPv6, and have no timeline for it either. There are transitional techniques, like NAT64 to connect to those hosts. Keep in mind that some ISPs only offer native IPv6, so lack of proper IPv6 support means go-apps become unusable. There's IPv6 support, but things like `conn, err := net.Dial("tcp", "google.com:80")` fail on IPv6-only hosts, because only an IPv4 connection is attempted.
- tptacek 12y agoWhat's the Golang IPv6 problem? (It does not seem weird to me that they'd prioritize functionality that everyone with a modern browser will be able to use versus functionality that quite possibly won't be useful to most Internet users ever.)
- chimeracoder 12y ago> versus functionality that quite possibly won't be useful to most Internet users ever.) You don't think that IPv6 is ever going to gain widespread adoption? Given how much of the US uses Comcast as their residential ISP alone, and how aggressively Comcast has been rolling out IPv6, I think we're near a tipping point[0]. Enterprise/business use will take much longer, but that's to be expected, as rollout for residential use has far fewer potential problems. (For the record, I did not downvote you). [0] http://www.google.com/intl/en/ipv6/statistics.html http://www.google.com/intl/en/ipv6/statistics.html
- wvh 12y agoI enabled spdy4 in Chromium on Debian "unstable" but the website doesn't seem to think it's on. What are we supposed to see?