![]() ![]() Its job is to field requests from clients for media sink availability, media route construction/destruction, and media route control via messaging. The Chrome Media Router is a browser service exposed in-process via C++ API and is exposed to other processes via a set of two Mojo interfaces: the Presentation interface and the Media Router API interface. The media router consists of four distinct components: Support for sinks that are not primarily intended to render media. Support for third party media route providers in Javascript or run-time installation of media route providers. Multicast of local content to multiple sinks at once. The following are non-goals but may be objectives for future work: Support the Cast Chrome Sender SDK on desktop and Android without any user installed extensions.Īllow new types of media sinks to be added to Chrome by implementing additional Media Route Providers. Support “flinging” HTML5 documents to remote devices capable of rendering them. Support mirroring locally rendered content to external screens, including on-screen and off-screen tabs, Chrome apps windows, and the system desktop. ObjectivesĪllow use of media sinks from a multitude of clients, including: Web applications via the Presentation API Chrome apps the browser itself and the Chrome OS system shell. Offscreen rendering, capture, and streaming of WebContents (required for full Presentation API support) will be covered in a separate design document. TODO: Add material on 1-UA mode, or add a separate document Presentation API functionality will be implemented in Chrome for Android using analogous platform components such as the Android Media Route Provider framework. Note that the non-Blink parts of the media router will be implemented only in desktop Chrome and ChromeOS. ![]() The Web application controls the content by two-way messaging. The content may be rendered locally and streamed to the display or rendered remotely. The Web Presentation API allows a Web application to request display of Web content on a secondary (wired, or wireless) screen. The media route can be terminated at user or browser request, which denies access to the media sink from the application. The media route allows the application to negotiate a peer-to-peer media streaming session with the media sink via messaging (e.g., via WebRTC or Cast Streaming), aka “mirroring.” The media route can also be used to request the remote display to render a URL without an associated peer-to-peer media streaming session, aka “flinging”. When a media source is linked with a media sink, a media route is created that allows two-way messaging between the source and the sink. The media router is a component in Chrome responsible for matching clients that wish to render media or URLs ( media sources) on devices and endpoints capable of rendering that content ( media sinks). TODO: Update with integration with Remote Playback API ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |