thanks so much for your good advice. look, i already code with node.js
and have an interesting prototype here:
https://www.videomail.io/
all i want is to improve the performance. i think i should do some
research with RTCWEB.
1. Browser retrieves a webpage with javascript in it.
2. Browser executes javascript, which:
1. Gets a handle to the camera using getUserMedia,
2. Creates an RTCPeerConnection
3. Calls "createOffer" and "setLocalDescription" on the
RTCPeerConnection
4. Sends an request to the server containing the offer (in SDP
format)
3. The server processes the offer SDP and generates its own answer
SDP, which it returns to the browser in its response.
4. The javascript calls "setRemoteDescription" on the
RTCPeerConnection to start the media flowing.
5. The server starts receiving DTLS/SRTP packets from the browser,
which it then does whatever it wants to, up to and including
storing in an easily readable format on a local hard drive.
makes sense but why so complicated? i want the node.js server to be
always listening for any new RTCPeerConnections and thus accepts any
incoming streams.
my second question is about the video format: in what format is the
video stream transferred and how can i store it in i.e. webm?
cheers
michael
Clearly, I've glossed over the details, but I hope that's enough to
get you in the right direction with a little more research on your end.
- do Mozilla and Chrome use different video codecs for the same
implementation?
Presently, both Mozilla and Chrome use VP8 for their video codec.
I am also confused, what's the difference between RTCWEB and WebRTC?
The standardization effort to enable real-time communications in web
browsers is a cross-organizational endeavor, with the
javascript-to-browser interface being defined in the W3C's "WebRTC"
working group, and the browser-to-network interface being defined in
the IETF's "RTCWEB" working group.
The term "WebRTC" is used in the press to refer to both halves of the
effort. You won't generally see "RTCWEB" unless someone is making a
specific reference to the IETF working group.
--
Adam Roach
Principal Platform Engineer
[email protected]
+1 650 903 0800 x863
--
Binary Kitchen
Michael Heuberger
4c Dunbar Road
Mt Eden
Auckland 1024
(New Zealand)
Mobile (text only) ... +64 21 261 89 81
Email ................ [email protected]
Website .............. http://www.binarykitchen.com
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
