为什么RTMP流协议的URL路径彼此不同？ [英] Why RTMP streaming protocal's url path different from each other?

问题描述

最近我正在处理RTMP流，即使用Flowplayer与Edgecast流服务和CloudFront流服务集成。

Recently I'm doing some work on RTMP streaming, that is using Flowplayer to integrate with Edgecast Streaming service and CloudFront Streaming service.

基本概念很容易遵循，但是不同提供商的格式确实浪费了我很多时间。

The basic concept is easy to follow, but the format of different providers really waste me a lot of time to figure out.

例如，为了使边缘广播感到高兴，根据文档，您需要以mp4：filename.mp4，flv：filename（不带.flv扩展名）和mp3：filename（不带.mp3扩展名）的格式指定文件名。

For example, in order to make edgecast happy, according to the documentation, you need to specify filename in the format of mp4:filename.mp4, flv:filename (without .flv extension) and mp3:filename (without .mp3 extension).

但是对于CloudFront，mp4：filename.mp4，文件名（没有flv：prefix和没有.flv扩展名）和mp3：filename（没有.mp3扩展名）是另外一个故事。

But for CloudFront, it's a different story that mp4:filename.mp4, filename (no flv:prefix, and no .flv extension) and mp3:filename (without .mp3 extension).

今天，当我尝试使用Edgecast的loadToEdge函数时，这种格式使人们更加沮丧，接受的格式为filename.mp4（不带mp4：前缀），filename.flv（不带flv：前缀）和mp3：filename.mp3

This format makes people even more frustrating when today I try to use Edgecast's loadToEdge function, the format the accept is filename.mp4 (without mp4: prefix), filename.flv (without flv: prefix) and mp3:filename.mp3.

如您所见，基本上那里没有逻辑，您必须猜测并尝试所有不同的组合以使其最终起作用。

As you can see, basically there is no logic there and you have to guess and try all different combinations to make it finally working.

我只想知道是否有人对为什么不同的提供者实施他们的想法有所了解以所有自定义方式流式传输？还是Adobe的错没有统一的形式，还是服务提供商可以使用他们喜欢的东西。

I just would like to know if anyone has idea about why different providers implement their streaming in all customized way? Or is it Adobe's fault doesn't have a unified form or it's just up to service providers to use whatever they like.

谢谢！

推荐答案

所有与实现有关。 URL格式（包括扩展名）与

It's all about implementation. The URL format, including extensions, has nothing to do with

类似，您的问题就像问为什么某些网站的URL与其他网站不同？ 提供图像的两种不同但可行的方法示例：

As an analogy, your question is like asking "Why do some websites have different URLs than others?" Example of two different yet viable ways of serving up an image:

• http：// server.com/question/87/why/65.png


• http://server.com/image/question?number = 87& image = 65 。

• http://server.com/question/87/why/65.png
• http://server.com/image/question?number=87&image=65.

有关EdgeCast，亚马逊等公司的编码人员如何实现其CDN的全部内容。我确定其中有些逻辑，是否经过深思熟虑。可能需要处理旧版系统，客户端和URL。

It's all about how the coders at EdgeCast, Amazon, et al wanted to implement their CDN. I'm sure there was some logic to it, well thought out or not. And probably some need to deal with legacy systems, clients and URLs.

它与FMS本身无关。就像上述类推的URL与其从其提供服务的网络服务器无关。

It has nothing to do with FMS itself. Just like the above analogy's URLs have nothing to do with the web server they are served from.

这篇关于为什么RTMP流协议的URL路径彼此不同？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！