본문 바로가기
기타

HTTP/2 - compared to HTTP/1, websocket (http1, websocket과 비교)

by 개발자종혁 2022. 2. 8.
728x90

http/2 vs http1

1. HTTP/2 is a binary protocol where HTTP 1.x is textual.

2. HTTP/2 is multiplexed to tackle a known limitation in networking known as head-of-line blocking (HOL Blocking).

3. HTTP/2 uses header compression to reduce overhead.

4. HTTP/2 Server Push allows servers to proactively send responses into client caches.

 

http/2 vs http1 - network speed

http 1.x - use Domain sharding which can be used to distribute resources across several domains.

 

 HTTP/2, we see the browser use a single multiplexed connection with a much faster load time.

 

HTTP/2 vs WebSocket

 
 
HTTP/2
WebSocket
Headers(헤더) Compressed (HPACK) None
Binary(바이너리) Yes Binary or Textual
Multiplexing(멀티플렉싱) Yes Yes
Prioritization Yes No
Compression(압축) Yes Yes
Direction(방향) Client/Server + Server Push Bidirectional
Full-duplex Yes Yes

 

Will WebSocket survive HTTP/2? (infoq.com)

 

Will WebSocket survive HTTP/2?

HTTP/2 is poised to eliminate much of the waste that developers deal with. Multiplexed connections will eliminate the need to bundle JavaScript libraries together. But is HTTP/2 a panacea to all our problems? What about WebSocket? Allan Denis tells us what

www.infoq.com

 

728x90

댓글