Webrtc, streaming application?

Recently appeared the interest to deepen the knowledge in the web. Actively developing web audio, webgl. At the same time found articles about webrtc, though as with the minuses and pluses was enough. Experience in writing applications with the transmission of video/audio data was not, therefore, interesting to try to realize this task.
Usually, such issues with zero experience is not particularly welcome, but what to do.... While I will try to do something on webrtc. But would be grateful to those who in General will tell you what to pay attention and will briefly point out interesting links.
June 26th 19 at 14:21
2 answers
June 26th 19 at 14:23
You have to start with webrtc.org and, of course, a specification
I had in my project to use it while still quite raw, many things are implemented is not very convenient.
Again requires a separate signaling channel, which automatically pulls WebSockets.
Many users are most of the time outside of your website that pulls the dependence in the form of Service Workers.
For conferences there are RTCMultiConnection, but I didn't like it. Thinking write your own solution.
The demonstration screen is made in the browser through one place and works only with the installation of add-ons.
Forgot to say that WebRTC is more or less normally only works in Firefox Nightly and Google Chrome. Recently I heard that Edge gash, but not yet seen in action. In October mitape promised that gash in Safari, but still working on it.
By the way, I wanted to add another project WebTorrent - there implements file sharing using RTCDataChannel. A very interesting idea in my opinion. Especially to reduce the level of traffic on the website.
Studied the issue "through one place" a couple of days ago, here is very well made in my opinion https://www.surfly.com/ - Felicita.Kertzmann99 commented on June 26th 19 at 14:26
: the website opens in an iframe. It's not a real sharing of screen. - raou commented on June 26th 19 at 14:29
Yes, but no "download/install", of course some websites, such as merchants, will not work. - Felicita.Kertzmann99 commented on June 26th 19 at 14:32
: I'm not saying the sites I'm talking about the normal screen sharing. For example, when I can show how I edit the file in Blender or configure any server or write the code. Maybe I do want the entire desktop to show and work with multiple programs.
Surfly is an analogue of the web shield from Yandex.metrics. - raou commented on June 26th 19 at 14:35
: thank you for your detailed response. But I understand that it's all the same standard and after a while many will go? - ryleigh27 commented on June 26th 19 at 14:38
: Yes, this will be the standard for web applications. - raou commented on June 26th 19 at 14:41
June 26th 19 at 14:25
There is no doubt that you need a bare WebRTC.

Because bare peer-to-peer WebRTC little to do - long poluchaetsya, passes the NAT, requires third-party or its TURN server, does not raise a normal one-to-many streaming, requires a signaling server to place calls.

Therefore, in order to start working with WebRTC, it is not strange, do not need to learn WebRTC itself.

Locate the platform or server with a high-level API that allows you to create flows and make calls via WebRTC.

For example:

stream.start('streamID'); //send the stream streamID
stream.subscribe('streamID'); //play the stream streamID
call.start('userID'); //call the user userID
call.pickup(); //accept call from userID

After you work with the platform, and possibly would not make sense to go deep into webrtc and enough top API functions. Or Vice versa, you'll need debajit inside WebRTC to implement some special functions.

Here are a few platforms that have API's for WebRTC streams and call

red5pro server
flashphoner - server
tokbox service
twilio service
voximplant service
is it possible to contact you personally for a paid consultation? - Felicita.Kertzmann99 commented on June 26th 19 at 14:28

Find more questions by tags Web DevelopmentProgrammingNode.jsWebRTC