Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

With http live streaming (HLS) we need to deliver video segments one after other to the player to play them in a continuous fashion. Segments are present on many streaming servers and we would load balance between these servers to deliver segment.

Assuming that every request for chunk hits our application server and we redirect to best possible delivery node, once we get a segment request. Will it lead to opening of many TCP Sessions for the HTTP request handling. For example, there would be 1500, HTTP chunk request (TCP Sessions) per user-session while watching a 2 hrs movie. If so this can be in-efficient and is there a way such that we would redirect every chuck request to the delivery node and maintains same TCP Session?

share|improve this question

No, Redirect means "make anotehr request". It is up to the client to implement (and the server to support) TCP keepalive between http requests, but it is totally out of the control of the server telling the client to get lost (i.e. redirecting him to some other server).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.