For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

The HTTP 2.0 War has Just Begun

#stirling Microsoft takes on Google as the war to win the standard for an overdue overhaul of HTTP starts to pick up steam RFC 1945 – “Hypertext Transfer Protocol -- HTTP/1.0” – was published in ...
Published Apr 11, 2012
Version 1.0
acceleration
application delivery
applications
availability
google
html 5
load balancing
management
microsoft
partner
Lori_MacVittie1's avatar
Lori_MacVittie1
Icon for Nimbostratus rankNimbostratus
May 30, 2012

Nagesh, 

 

WebSocket is going to run into the same issues as SPDY (and as you point out, has similar benefits). The biggest difference being the lack of headers in WebSockets, which is going to have a much bigger impact on infrastructure (network and server) as all objects must be inspected to determine their content-types... 

 

I have discussed HTML5/WebSockets in the past here: https://devcentral.f5.com/s/articles/oops-html5-does-it-again and here: https://devcentral.f5.com/s/articles/html5-web-sockets-changes-the-scalability-game

 

but you raise a valid point, it may be time to compare to SPDY and S+M, which are similar in core premises. 

 

Thanks! 

Lori

 

ed. LZ. updated poorly translated links.