Browse Source

notes on how code will be layed out and how the flow works..

main
John-Mark Gurney 5 years ago
parent
commit
9da1b63d8f
1 changed files with 25 additions and 0 deletions
  1. +25
    -0
      ARCHITECTURE.md

+ 25
- 0
ARCHITECTURE.md View File

@@ -0,0 +1,25 @@
web server component -- rendezvous part, and mixing/aggregation

web client component -- connect to server, send encoded data

Meeting setup flow:
1) Admin uses server to generate room. The server generates
a URL and the admin gives out url to participants.
As part of this, restrictions may be applied, such as when
the meeting is valid.

Participant flow:
1) Participant goes to meeting url obtained from admin.
2) Once meeting is valid, setup the following:
a) WebRTC data connection to server
b) Input audio
c) Output audio
3) Pass the setup items to do encoding/decoding and playback.


File information:
src/index.js -- main file for web page

Random references:
navigator.mediaDevices.getSupportedConstraints();
https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getSupportedConstraints

Loading…
Cancel
Save