< p>I think hixie- and hybi- are the previous drafts, and the RFC is the “last word” of all implementations that will eventually converge. However, I was surprised to find that the RFC started in December 2011, and the latest hybi -*It started in February 2012.
Can someone please some highlights? What is the historical development of all these branches? What is the roadmap for the future?
So, what do those interesting names (hixie and hybi) stand for?
“Hybi” is derived from “hy_pertext bi_directional”.. IETF working group “bidirectional or server initiated HTTP (active WG)”.
The latest and final RFC is RFC6455 . Realize this.
Hixie-75/76 has been deprecated, there are security vulnerabilities, and the outdated version has been used for a while.
Hybi-Draft-N.. Among them N is…,10,..,18 mark the revised protocol during the development of the final RFC of the draft RFC.
Everything> = Hybi-10 is just a small variant of the final RFC6455.
In short: read and implement http://tools.ietf.org/html/rfc6455, you will be fine.
I recently learned that there are many WebSockets Protocol specifications (one of them is called hixie-, the other is hybi-, and finally RFC 6455).
I think hixie- and hybi- are previous drafts, and RFC is all The implemented “last word” will eventually converge. However, I was surprised to find that the RFC started in December 2011, and the latest hybi-* started in February 2012.
Can someone please some highlights? What is the historical development of all these branches? What is the roadmap for the future?
So, what do those interesting names (hixie and hybi) stand for?
“Hixie” is derived from Ian Hickson.. The original proposer/author of the WebSocket protocol.
“Hybi” source Since “hy_pertext bi_directional”.. IETF working group “bidirectional or server initiated HTTP (active WG)”.
The latest and final RFC is RFC6455. This is achieved.
Hixie-75/76 has been deprecated, there are security vulnerabilities, the outdated version has been used for a while.
Hybi-Draft-N .. where N is…,10,…,18 signs The revised protocol is during the development of the final RFC of the draft RFC.
Everything> = Hybi-10 is just a small variant of the final RFC6455.
In short: read and implement http:/ /tools.ietf.org/html/rfc6455, you will be fine.