Re: [Wish] Lecturing and WebRTC

[Lorenzo Miniero <[e-mail]>]

On Tue, 09 Mar 2021 19:03:00 +0100
Juliusz Chroboczek <[e-mail]> wrote:

> > Take node that tipical wish publishers are going to be tools like
> > ffmpeg or OBS,  I doubt they will provide the flexibility you are
> > looking for.  
> 
> I think the requirement is on the receiver.  What will the protocol
> allow my implementation to publish?
> 


But receivers are actually out of scope, here. WISH will just specify
how a media publisher can send media to a server via WebRTC. How you
then distribute the media is entirely up to you (it may not even be via
WebRTC, e.g., if you're transcoding to use an HLS CDN). In your case,
WISH basically provides an alternative way by which the teacher can
send media to your Galene media server: how you distribute the streams
to students via WebRTC is up to you (you may even decide to pack them
all together into a single PeerConnection yourself, for instance).

 
> > Anyway, as said before, this case could be implemented by assigning
> > one url to each stream (which could be even send from different
> > devices) and managed at service level.  
> 
> How do you envision interoperability between independently developed
> clients?
> 


In this case, the only interoperability that really matters is between
those that will write the publishing clients, i.e., the endpoints
encoding and sending the media (OBS, FFmpeg, GStreamer, or a web
application), and those that will write the media servers receiving the
media (Galene, Janus, Medooze, or whatever else).

If you design your WISH server to expose three different endpoints for
the media streams you want to publish, then I think Adam's point is
that you can use any WISH client to push the media you want to the
endpoint you want, knowing that as a media server/service you'll have
the info you need to properly map them to the "right thing" when
distributing it.

Lorenzo

-- 
I'm getting older but, unlike whisky, I'm not getting any better
https://twitter.com/elminiero