News for hackers. Stuff that matters.
Re:HTTP/2.0 — Bad protocol, bad politics by akerl_ on Wednesday January 07, 2015 @09:58AM (#8850769)
I believe that browser vendors will push technology that benefits them. That's definitely not in dispute. But you need to convince them that HTTP/2.0 is beneficial to them, and I don't think that will be easy if content providers aren't serving content via HTTP/2.0.
Re:HTTP/2.0 — Bad protocol, bad politics by tracker1 on Wednesday January 07, 2015 @03:20PM (#8853031)
Most of the enhancements I'm aware of HTTP/2 are centered around SPDY.. along with persistent connections. The upconvert for SPDY and WebSocket connections are interesting on HTTP/1.0, I kind of wish that this had worked hand in hand with DNS to allow for DNSSEC publishing of public encryption keys for use with HTTP, then HTTP negotiating against that key.

I also wish there were layer between full encryption for content that is intended to be available for http and https (without the extra overhead) for signed content.

Re:HTTP/2.0 — Bad protocol, bad politics by ibotty on Thursday January 08, 2015 @02:12AM (#8855336)
What you want re public keys in dnssec secured DNS is called Dane. Browsers are slow to implement it though.