If you watch the video starting at the 20:00 mark, he explains it.
Basically, this technology allows users to connect to each other through their web browsers. They don’t use a “server” middleman relay or third party application. Rather, they use a connection site/location on the Net to send and receive data.
Here’s a primitive diagram of what I’m trying to say.
Traditional Server/Client Relay
(FB User A) <~> (FB Server) <~> (FB User B)
- The Server relays what is sent and received.
- The Server can copy what is sent and received.
- The Server can stop the traffic, and or shut down your site, blog, post at any time.
- Both users have to be using the same application, in this case, it’s Facebook’s web interface.
WebRTC
(Firefox Browser) <~> (Bridge Connection Site URL) <~> (Chrome Browser)
At 31:00 he explains how the web connection works.
- Because the connection is more direct, traditional server limitations are removed from the equation.
- It’s the difference between playing a laggy game on WOW (World of Warcraft) and a super fast Halo LAN party.
- The controlling server is replaced with any connection site. Both users just need to tell each other where to meet on the Internet via URL address.
This is similar to my proposed idea to use a seamless web interface for different functions. I customize the sites reaction to your MPID. They customize the functionality based on the site they agree to meet-up.
The biggest advantage is a better user experience, faster data transfers, less restrictions, single click use, etc. There could also be an infinite number of other advantages we haven’t discovered yet.