Versions Compared

Old Version 10

changes.mady.by.user Dmitry Bezheckov

Saved on

compared with

New Version 11

changes.mady.by.user Dmitry Bezheckov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A few words about demo client in browser - it's written on JS and supports our signal server.

but It also can be improved via using some cross-browser library for RTCPeerConnection (https://github.com/otalk/rtcpeerconnection).

Native client and MCU server

As I mention in Our signal server chapter the RTCPeerConnection API is oriented on p2p connections but It allows to create client-server solutions because OM works on server-client architecture.

 

I've tryed to create RTCPeerConnection on java but there aren't any java api for this purposes.

There are only js api and some abandoned demos in the Internet but I've found the repository with native (c++) webrtc peerConnection api for browsers.

This native api includes java api for android. But It also broken, you can see explanation here - https://groups.google.com/forum/#!topic/discuss-webrtc/BUPq2UxIyq8.