<P> However, these criticisms have been outweighed in practice by the economics and scalability of HTTP delivery: whereas non-HTTP streaming solutions require massive deployment of specialized streaming server infrastructure, HTTP - based adaptive bit - rate streaming can leverage the same HTTP web servers used to deliver all other content over the Internet . </P> <P> With no single clearly defined or open standard for the digital rights management used in the above methods, there is no 100% compatible way of delivering restricted or time - sensitive content to any device or player . This also proves to be a problem with digital rights management being employed by any streaming protocol . </P> <P> The method of segmenting files into smaller files used by some implementations (as used by HTTP Live Streaming) could be deemed unnecessary due to the ability of HTTP clients to request byte ranges from a single video asset file that could have multiple video tracks at differing bit rates with the manifest file only indicating track number and bit rate . However, this approach allows for serving of chunks by any simple HTTP server and so therefore guarantees CDN compatibility . Implementations using byte ranges such as Microsoft Smooth Streaming require a dedicated HTTP server such as IIS to respond to the requests for video asset chunks . </P>

Adaptive bitrate streaming for an ott video provider