4 ms·
This is a really good introduction to how video works. The only think I find missing from a production OTT environment is DRM. Also I assume when the author say
by arkj 5y ago
This is a really good introduction to how video works. The only think I find missing from a production OTT environment is DRM. Also I assume when the author says "http" he means "https" there are very few (I knew only one and even they used https termination by Akamai) providers who use "http" these days for streaming even with DRM.
If anyone is building an economically viable OTT platform they should consider building their own CDN. Insiders tell me the Singapore based OTT provider HOOQ went bankrupt paying huge bills to AWS and Akamai.
- capableweb 5y ago> Also I assume when the author says "http" he means "https" there are very few (I knew only one and even they used https termination by Akamai) providers who use "http" these days for streaming even with DRM. For what the guide is, I think HTTP is accurate enough, as HTTPS is not its own protocol, it's always HTTP+TLS/SSL, so just saying HTTP is good enough. The ones that need to add the extension, will know so. For video editors (and other parts of the target for this guide), it's more than likely superfluous information. Also, as far as I know, DRM and HTTPS have different use cases. The DRM we see in browsers are around controlling playback on the client device, not encrypting the content to/from the media server/client device, while HTTPS is the opposite. So if they are using DRM or not doesn't matter when we talk about using HTTPS or not.