Hacker News new | past | comments | ask | show | jobs | submit login

A draft of the SPDY specification is here:

http://dev.chromium.org/spdy

Mike Belshe presented about SPDY in the IETF HTTP working group meeting at the most recent IETF meeting:

http://www.ietf.org/proceedings/80/slides/httpbis-7.pdf

We'd love for more folks to implement SPDY, both clients and servers.




Sounds like HTTP 1.2?

Since Google servers and Chrome already support it, the chicken-egg problem might be solved. Firefox has an incentive to implement it to make Google search faster and other web service should implement this to provide a smoother user experience.


HTTP 2.0      (1.2 would have to be backwards compatible)


Yes. And just to argument this, here is the relevant except of the FAQ:

Q: Is SPDY a replacement for HTTP?

A: No. SPDY replaces some parts of HTTP, but mostly augments it. At the highest level of the application layer, the request-response protocol remains the same. SPDY still uses HTTP methods, headers, and other semantics. But SPDY overrides other parts of the protocol, such as connection management and data transfer formats.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: