Article didn't mention it, but Justin's blog post did:<p>"Standards-based: XMPP, Jingle, RTP"...<p>We're working on publishing the spec, which should be available soon. In fact, it's already implemented in libjingle:<p><a href="http://code.google.com/p/libjingle" rel="nofollow">http://code.google.com/p/libjingle</a>
<i>P2P can introduce latency</i><p>Can someone explain this to me? I guess if your video has to go via multiple hops, that would be laggy, but if you connect directly to each peer in the conversation surely that would be <i>less</i> laggy than a client-server architecture?
I think "the hint" of the amazing technology behind Google+ Hangouts would be more appropriate.<p>Could one of the people involved please publish a more detailed blog posts as how all these pieces are linked together. The tweaker in me wants to start fiddling with it ASAP:<p>Fully browser-based/cloud-based<p>Client-server: leverages the power of Google's infrastructure<p>Designed for low latency (< 100 ms) and high performance (multicore + hardware acceleration)<p>Standards-based: XMPP, Jingle, RTP, ICE, STUN, SRTP<p>Fully encrypted (HTTPS + SRTP)
Flash has had peer-to-peer video support for 3 years now and it's available to 90%+ users on the web. Chatroulette was built in 2 days around this technology. Whenever "standards" catch up to Flash, it's being touted as "amazing".