Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Initial version of the interoperability document #175

Merged
merged 3 commits into from
Aug 31, 2015
Merged

Initial version of the interoperability document #175

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5d28d71
Initial version of the interoperability document according to the dis…
louaybassbouss Aug 27, 2015
420d3d3
* Fix typos
louaybassbouss Aug 27, 2015
042483e
* Fix typos
louaybassbouss Aug 28, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added images/interoperability-1ua.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/interoperability-2ua.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
42 changes: 42 additions & 0 deletions interoperability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# Assess interoperability of Presentation API implementations

This document discusses the interoperability of potential Presentation API implementations in particular interoperability
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a nit-pick, but wrapping the text with shorter lines will make future diffs easier to read.

between user agents in case of [2-UA implementations][2ua] and between user agents and wireless/dump displays in case of [1-UA implementations][1ua].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/dump/dumb/s?

For this, state of the art technologies and standards that may be useful to implement the Presentation API will be considered.

> TODO: fix links of 1-UA and 2-UA implementations in the text
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed with #176


## Interoperability between user agents

The following diagram shows an overview of the main components for the 2-UA implementation. Each of the user agents implements
part of the Presentation API (for controlling browsing context or presenting browsing context). To ensure interoperability
between user agents running on controller devices and user agents running on presentation devices the following aspects should be considered:

* **Discovery**: To discover presentation devices, the controlling user agent should use the same technology as the presenting
user agent use to advertise itself. Potential technologies: SSDP, mDNS or BLE (BLE Beacon)
* **Launch**: After discovery, the controlling user agent should know how to launch a new presentation or join an existing one.
Common message formats should be also used. Potential technologies: DIAL (uses SSDP for discovery), Google Cast (part of it).
* **Communication**: Also for communication both user agents should use same technologies/protocols to ensure interoperability.
Potential technologies: WebSockets, WebRTC, Raw Socket, Google Cast (part of it)
* **Signaling**: common language and message formats (e.g. using JSON or XML) should be used to exchange signaling information between the two user agents.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add security to implemenent authentication of the display and privacy of the presentation messaging.

![2-UA implementation][2ua-img]

## Interoperability between user agents and dump displays

The following diagram shows an overview of the main components for the 1-UA Implementation. There are less requirements
as in the 2-UA case to ensure interoperability between controlling user agents and presentation displays.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be helpful to list the specific protocol components, as was done above. In my mind this includes:

  • Discovery (as above)
  • Signaling (to establish/negotiate the display protocol and the media transport)
  • Transport (to format the media stream for the network)
  • Codec (to encode/decode the content into a media bitstream)

The controlling user agent implements the Presentation API for both controlling and presenting browsing contexts and the presentation
page is rendered in silent mode (not visible for the user). The user agent captures the UI output of the presentation page rendered
in silent mode and sends the frames to a presentation device like a projector or wireless display. This means the user agent and the
presentation device should use a common streaming technology to ensure interoperability. More than likely, the user agent will use System APIs
offered by the OS to show content on the presentation device. But other technologies not offered directly by the OS are also possible, for example
Google Cast extension for chrome support Tab cast to Chromecast using WebRTC. **Potentials Technologies**: HDMI, Intel WiDi, Miracast, Airplay, MHL.


![1-UA implementation][1ua-img]

[1ua]: http://w3c.github.io/presentation-api/#1-UA
[2ua]: http://w3c.github.io/presentation-api/#2-UA
[1ua-img]: ./images/interoperability-1ua.png
[2ua-img]: ./images/interoperability-2ua.png