Pick all that apply

• 1Choice 1.

  HLS cuts the audio into short segment files delivered over HTTP, so it rides CDN caches as-is, and adaptive bitrate streaming (ABR) that changes bitrate with network conditions is possible

• 2Choice 2.

  Because HLS is fetched segment by segment, the default setup has several seconds to tens of seconds of latency, and to cut it you shorten the segments or use LL-HLS (Low-Latency HLS)

• 3Choice 3.

  WebSocket handshakes over HTTP and then keeps one TCP connection open in both directions, so for frequent small messages like chat it's more efficient than polling, which repeats the connection and headers on every request

• 4Choice 4.

  Unlike HTTP, WebSocket doesn't support TLS, so chat messages have to be encrypted separately in the app

• 5Choice 5.

  To play HLS with AVPlayer, the app has to download the segments itself with URLSession, decode them, and hand them over