You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "SebastianWagner (JIRA)" <ji...@apache.org> on 2016/05/03 06:27:13 UTC
[jira] [Updated] (OPENMEETINGS-1353) Change OM architecture from
central server to p2p via webRTC
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner updated OPENMEETINGS-1353:
------------------------------------------
Assignee: Dmitry (was: Maxim Solodovnik)
> Change OM architecture from central server to p2p via webRTC
> ------------------------------------------------------------
>
> Key: OPENMEETINGS-1353
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1353
> Project: Openmeetings
> Issue Type: Improvement
> Reporter: Dmitry
> Assignee: Dmitry
> Labels: gsoc, gsoc2016, java, mentor
>
> Now OM is using central server for all rooms and hence work slow if a lot of clients are active.
> We can change this with p2p webRTC way.
> I suggest to use full-graph topology for clients because this is simple one.
> You can try it this:
> http://cdn.peerjs.com/demo/videochat/#
> A lot of examples are available this to present webRTC capability : https://webrtc.github.io/samples/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)