A user on the subway keeps bouncing between Wi-Fi and LTE, and your app's requests keep dropping. How do HTTP/2 over TCP and HTTP/3 over QUIC each handle that?
A TCP connection is bound to the IP 4-tuple, so a network change kills it and you pay a fresh handshake (1 to 2 RTT plus TLS). QUIC identifies the connection by a connection ID, so it survives a path change and can resume with 0-RTT.
CS fundamentals and algorithmsShort answerIntro
What's the difference between TCP and UDP? When a packet is lost, what happens under each…
#quic #tcp #urlsession
NetworkingShort answerIntro
You've inherited an app that does all its networking through URLSession.shared. Can you…
#urlsession
NetworkingMultiple choiceBasics
Select all the statements that correctly describe HTTP/2 compared with HTTP/1.1.
#urlsession
NetworkingShort answerBasics
The legacy code has a function that waits on a URLSession response with DispatchSemaphore…
#urlsession