171–180 of 242 posts
Earlier quoted context omitted.
until it is widely used and supported, there is a big cost to adding features to a CDN. the means dont justify the ends.
And how is it supposed to be used if CDNs don't support it? Sounds like a circular dependency to me. Technology is here, but without infrastructure it's close to impossible to use at scale.
ok, are Google planning on supporting HLS if they're ditching flash? I see this site is saying that it does (with their player) -- so does it natively or are these guys doing a transmux in Javascript similar to HLS.js and others?
Earlier quoted context omitted.
And how is it supposed to be used if CDNs don't support it? Sounds like a circular dependency to me. Technology is here, but without infrastructure it's close to impossible to use at scale.
You cut flash out and then the need to support it pops up.
Google worked around it by rolling out their own CDN. Do you propose to do the same?
Getting really frustrated with all the things chrome is starting to change. We are starting to become a bunch of sheep, if google wants something, they announce it, and implement it, we developers, users have to fall in line and start doing everything they want. What the hell is going on, why are we not pissed off about this. Look I hate Flash as much as the other guy, but blocking an extention just because a company…
>Look I hate Flash as much as the other guy, but blocking an extention just because a company doesn't like it. It's their browser, they can do what they like.
Oh the US government is spying on its own citizens? It's their country, they can do as they like.
Steve Jobs was right ... 6 years ago.
Earlier quoted context omitted.
You cut flash out and then the need to support it pops up.
Catch 22. To cut Flash out you need to use DASH + MSE. You come to CDN and say you need it, and they say they don't support it because you first need to use it... Google worked around it by rolling out their own CDN. Do you propose to do the same?
Earlier quoted context omitted.
Catch 22. To cut Flash out you need to use DASH + MSE. You come to CDN and say you need it, and they say they don't support it because you first need to use it... Google worked around it by rolling out their own CDN. Do you propose to do the same?
The first CDN to support it will get the clients.
Earlier quoted context omitted.
"Open Web" includes online commerce. It's still open even though people use HTTPS-encrypted data streams, for example.
Browser makers don't need to get a certification to use HTTPS.
The notion that some parts of the web standard are pay-to-play is actually not new.
Earlier quoted context omitted.
Netflix can make its own app, outside the web.
One of the most attractive features of netflix is the ability stream movies on the browser. Why would we want to move that to a separate app?
In Chrome and Firefox, you can't watch Netflix above 720p. It's why I must use IE with Silverlight to watch Netflix at full HD on Windows 7.
Earlier quoted context omitted.
Maybe I'm naïve or not seeing something here but DASH looks like something you can do by storing a couple of files somewhere and setting a MIME type [0]? What's special about DASH that CDNs need to specially support it? Or are you talking about services that handle transcoding video and such as well? [0]: https://developer.mozilla.org/en-US/docs/Web/HTML/DASH_Adapt...
From what I understood, CDN is needed to lift the heavy load from the source servers. Without them you'd be hammered by heavy traffic, and not only that, the route to the end user will be most likely longer. DASH is adaptive streaming, and as such, when you select some stream from the client, CDN should support that in their infrastructure (including codecs and etc.). I don't know the details exactly, but it's far fr…
This makes sense if the CDN is transcoding the video for you but if you do that yourself I don't think a special CDN is necessary.
From Mozilla [0]:
> DASH works via HTTP, so as long as your HTTP server supports byte range requests, and it's set up to serve .mpd files with mimetype="application/dash+xml", then you're all set.
And from encoding.com [1]:
> To play the content, the DASH client first obtains the MPD. The MPD can be delivered using HTTP [...]
> Using this information, the DASH client selects the appropriate encoded alternative and starts streaming the content by fetching the segments using HTTP GET requests.
This definitely sounds like it doesn't need any special support from the server. As long as it can serve files over HTTP, the only special thing is the transcoding and setting up the manifest, which doesn't need to be done by the CDN.
I have a feeling CDNs advertise support for HLS and Adobe's streaming because they require additional support.
[0]: https://developer.mozilla.org/en-US/docs/Web/HTML/DASH_Adapt...