Re:The amazing technology behind Google+ Hangouts
by nl on Thursday June 30, 2011 @11:58PM
(#2716992)
P2P can introduce latency
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 less laggy than a client-server architecture?
Re:The amazing technology behind Google+ Hangouts
by suprgeek on Friday July 01, 2011 @03:21AM
(#2717372)
I think "the hint" of the amazing technology behind Google+ Hangouts would be more appropriate.
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:
Fully browser-based/cloud-based
Client-server: leverages the power of Google's infrastructure
Designed for low latency (< 100 ms) and high performance (multicore + hardware acceleration)
Re:The amazing technology behind Google+ Hangouts
by protagonist_h on Thursday June 30, 2011 @05:44PM
(#2715854)
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".
"Standards-based: XMPP, Jingle, RTP"...
We're working on publishing the spec, which should be available soon. In fact, it's already implemented in libjingle:
http://code.google.com/p/libjingle
I have to wonder if it's based on Muji or if it was built from scratch.
EDIT: Never mind, found it in the article. http://juberti.blogspot.com/2011/06/announcing-google-hangou...
EDIT 2: Oh, you're a Googler. Good to see that you'll be opening it up. :D
I wonder if that's just a Google-internal thing or if Google+ will embrace other social networks wanting to integrate.
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 less laggy than a client-server architecture?
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:
Fully browser-based/cloud-based
Client-server: leverages the power of Google's infrastructure
Designed for low latency (< 100 ms) and high performance (multicore + hardware acceleration)
Standards-based: XMPP, Jingle, RTP, ICE, STUN, SRTP
Fully encrypted (HTTPS + SRTP)
http://peter.sh/2011/06/flexbox-web-sockets-inclusion-of-web...
Great blog btw, I check it each week to see what's cooking under the hood of Chrome :-)