HTTP vs. WebSocket

x

WebSocket vs. HTTP benchmarks http://blog.arungupta.me/rest-vs-websocket-comparison-benchmarks/

HTTP

__ is not good for real time applications because each connection must be opened and closed, which creates network overhead.

REST

When an application only needs to update when a user takes action, using __ architecture with HTTP is more efficient than using WebSocket because connections are infrequent.

TCP

Each HTTP request creates and closes a single __ connection, while WebSocket maintains this connection for the lifecycle of the connection.

x

Explanation of WebSocket https://www.pubnub.com/blog/2015-01-05-websockets-vs-rest-api-understanding-the-difference/

uni, bi

HTTP is __-directional while WebSocket is a __-directional protocol

header, 2

HTTP sends a lot of byes in the __ of each message, while WebSocket frames the data with __ bytes.

x

Overview of protocols: https://stackoverflow.com/questions/14703627/websockets-protocol-vs-http

x

Socket.IO vs WebSockets: https://codeburst.io/why-you-don-t-need-socket-io-6848f1c871cd

full-duplex

The __ aspect of WebSocket means the client and server communicate independently. There is no request/response cycle.

false. There are advantages and disadvantages to both

True or false: WebSocket should replace HTTP as the default communication protocol.

ful, less, vertically, horizontally

WebSocket is a state-__ protocol while HTTP is a state-__ protocol. This means that WebSocket will scale well __ while HTTP scales better __.

polling

With HTTP, __ is the process where the browser sends periodic requests to the server to see if there is new information. This is needed because the server cannot send information to the browser.

WebSocket

With the __ protocol, information can be pushed to the browser on demand in real time because the connection stays open.