Hi, I agree that if FirefoxOS do not provide a way to implement RTSP, Venders are going to implement it by own ways, because it is necessary for products. And MediaElement approach is suit for RTSP, I think.
When FirefoxOS succeeds as a mobile platform, a lot of venders are going to implement a lot of existing multimedia capabilities on FirefoxOS. For example, mobile TV capability needs to be implemented in FirefoxOS. In Japan, it is one of the very important capabilities. Right now, there are no guidences about how to implement it. It needs a lot of APIs and capabilites. Then MediaElement approach do not fit to it, I think. But if we do not provide a way to implement it. Each venders are going to implement it by their own ways. I know that it is not so difficult to implement them, if there are already C/C++ implementation in android. We should provide these APIs and implementations like WebFM if they are important capabilities for mobile phones. And need to provide media server process capabilities in gecko in future. Regards, Sotaro ----- Original Message ----- From: "Thinker K.F. Li" <[email protected]> To: [email protected] Sent: Friday, February 1, 2013 11:14:45 PM Subject: Re: HTML Media support and format proliferation on Firefox OS, Android and Desktop Fabrice Desre <[email protected]> writes: > On 02/01/2013 02:19 AM, Thinker K.F. Li wrote: > >>> Right, I think there's a misunderstanding. When I said "local apps" I >>> meant a web app that exists on the device vs a web page on the >>> internet. I'm not saying using a native app to play these formats. >>> I'm saying only web applications installed on the device can use them. >> >> How can we implement RTSP in a web application? Do you have any idea? >> > > You don't implement RTSP in the web application itself (or maybe you can > with tcp socket and canvas, I don't know the protocol well enough). You > implement it on the platform side, and we check at run time if the > requesting document is part of a privileged or certified app to allow > the resource to be fetched and played. I don't think we can make a useful player in the web application itself if it is possible. We can use websocket and canvas in a web applicaion, but it also means to implement codecs in JS. It may be workable for desktop for people having good high-end PC, but it is not for mobile devices. For MediaElement approach, it means checking if the requesting app allowed to play RTSP stream at MediaElement. If we don't go MediaElement approach, we will do it in a approach that we don't like others to follow. I afraid that eventually hardware vendors will find it is a easy way for them to integrate exisiting media player on their platform. Then, I can foresee a lot of vendors integrate their platforms in this way. -- Sinker -- 天教懶漫帶疏狂 _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
