3 ms·
So your startup will basically do what videojs.com (http://videojs.com/ http://videojs.com/) does + DRM? I guess it could work but maybe very easy to duplicate.
by Thomaschaaf 15y ago
So your startup will basically do what videojs.com (http://videojs.com/ http://videojs.com/) does + DRM? I guess it could work but maybe very easy to duplicate. At least from how I understand your approach.
P.S.: Bing Cache works
- Keverw 15y agoNo. It's a video on demand service. Also planning on doing live channels and some other stuff. Right now our plan is to serve content in HTML5 but it doesn't really have DRM. So I think that will limit the content we can get from studios.
- deleted 15y ago[deleted]
- dmethvin 15y agoAbsolutely it will limit what studios allow--as in the major studios will allow nothing. HTML5 video only supports standard HTTP download of a single unencrypted stream, and I'm not clear on how a token scheme will provide any real security for that unencrypted stream. There are the bandwidth-divining problems since you'll want a higher quality stream on a fast connection than a slow one and HTML5 video has no built-in way to do that. On iOS you can use HTTP Live Streaming via Safari, but if you depend on that you're locked into a single platform. What is driving your startup to use HTML5 video? Are you trying to avoid licensing fees for DRM technologies? A lot of these problems can be overcome if you build an app, perhaps it's possible to use a hybrid approach in PhoneGap so you can maintain a HTML UI but play video via a proprietary video library that supports DRM.