The multimedia streams are delivered using the Real-time Transport Protocol (RTP).
If needed, NAT traversal is assisted using Interactive Connectivity Establishment (ICE).
This year we are fortunate to be working with four great students, and everyone has already produced code samples (some of them merged, some of them […] Yes!
You as the developer would have to write different code for every browser that you plan to support. The API that it exposes is easy to use and understand which makes it a really great candidate for implementing cross-browser Web RTC. The reality is that there’s always a server which bridges the connection between peers.
Two or more devices can’t just magically create a connection out of thin air.
What it does is act as a wrapper around the browser’s Web RTC implementation.
As you might already know, browser vendors doesn’t exactly agree on a single way of implementing different features which means that for every browser there’s a different implementation for Web RTC.