WebRTC/media-streaming with Presentation API?

Aperta
  • Qualcosa non va?
#240 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
documentation

Direzione di ricerca

Start with the Streaming Protocol in section 9, the Presentation API requirements, and the related issues #117 and #84 named in the issue. The request raises open design questions about WebRTC, QUIC, and how streaming relates to Presentation and Remote Playback, without identifying a specific change or acceptance criteria; a clear direction would require the project to decide those questions.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

v2

WebRTC / Presentation API media-streaming

Hello all. Coming to this spec & curious about how media across Presentation API devices would work. Is WebRTC is usable within OSP, & is that how such a use case would work, or is it intended that the Streaming Protocol is usable within Playback API? Is there any cross-integration between Streaming Protocol and WebRTC? Can OSP help set up QUIC connections that tools like WebTransport & other or future webrtc-quic work might leverage?

As a web developer trying to work with multimedia across multiple devices, I'd normally rely on WebRTC to, for example, have two user-agents share webcams with one another inside an HTML experience. If those tools & skills were portable into an OSP experience, that would be great. If not, can Presentation controllers and a receiver share video with each other via some other means?

relation to #117, streaming protocol

How if at all does this ask relate to this action item from May 15, 2018 Berlin F2F, mentioned in #117:

@mfoltzgoogle to open an issue on how to map WebRTC on the control protocol for media streaming

#117 was closed this past summer, declaring that, "OSP now has a streaming protocol (section 9, "Streaming Protocol."). This can be closed.".

I was initially hoping this implied that WebRTC needed to map atop the control protocol, but I'm not sure if I understood the original intent, & whether that intent in OSP has changed over time or not?

relation to webrtc-quic work

How do these use cases & desires relate to ongoing work in QUIC API for P2P connections and web-transport work, originating from this presentation mentioned in #84?

To me, there is some crude, approximate resemblence between what Streaming Protocol does & the QuicTransport interface, in that each works somewhat as a container for a bunch of different streams. Ideally as a developer I'd like to see some way for OSP devices to initiate these emerging standard communication technologies with each other.

developer experience with Streaming Protocol

At the risk of wandering further away from this Presentation API / WebRTC-oriented interest, I'd say in general I don't really understand what context the Streaming Protocol exists in, what it's for. It seems like it's a way to send audio & video & data, but where-as Presentation API & Remote Playback give me a sense of how & what the user experience would look like, I do not understand how & what Streaming Protocol is for: it's a protocol, an abstract capability, & I'm not sure how or where or who or what uses it. It would be helpful if the spec mentioned Streaming Protocol in the introduction or in general before [§ 9. Streaming Protocol](https://w3c.github.io/openscreenprotocol/#streaming-protocol Streaming Protocol).

My guess is that Streaming Protocol underlies a means for OSP Remote Playback & Presentation API to work, but I'm not sure how or where these developer-facing means get specified in terms of underlying Streaming Protocol interactions.

update Playback API requirements?

Ideally I'd like to see streaming media added to the Presentation API requirements. At the moment I'm not sure if it is a design goal or possibility or not.

Any further information about how these other upcoming technologies mix in with OSP would be good to hear too. Thank you, godspeed, I have high hopes this technology can send us all to fantastic new places.

Lingua principale
Bikeshed
Stelle
115
Fork
21
Merge medio
5h 2m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di w3c/openscreenprotocol

Tutte le issue di w3c/openscreenprotocol

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.