31–40 of 50 posts
Earlier quoted context omitted.
I'm pretty sure Gmail still uses flash for the audio but I could be wrong.
I mean, I could be wrong, but any of the A/V functionality in Gmail requires that I install a DEB in Ubuntu and it works fine with click-to-enable flash (obviously I'm not enabling it on gmail :P)
Well, I am not sure why Google went with XMPP when the rest of the telecom and networking industry is gravitating towards IETF SIP as signaling protocol. There are so may overlaps in both of them in the sense that they use the same components such as SDP and ICE. Can anyone from Google or otherwise throw some more light on - Why Google prefers XMPP over SIP - In what areas XMPP is better that SIP I am not stating tha…
There are extensions for vCards. There are extensions for PubSub.
XMPP works over HTTP using BOSH. It can also work over SOCKS.
Apache/Google Wave uses XMPP for federation. It is just flat out more extensible and featureful. Just like the acronym stands for: Extensible Messaging and Presence. It does a whole lot more than just IM or just VoIP.
http://xmpp.org/xmpp-protocols/xmpp-extensions/ http://en.wikipedia.org/wiki/Apache_Wave#Federation_Protocol
Can iChat speak Jingle? I just tried the combination of web-based Gmail iChat and the web client can see that the iChat client has a camera and I can initiate a call but iChat never shows an incoming one. If I go iChat iChat over Google's XMPP server I can make a call. Does iChat speak yet another incompatible video call extension if it used with an XMPP network? Adium can't do AV either.... Can anyone recommend a OS…
Earlier quoted context omitted.
In light of interoperability, could you please address the Google rationale for going with XMPP rather then SIP, as there is considerable support for SIP in existence, e.g. IMS on 4G networks, VoIP providers, PSTN gateways, Skype Connect, etc.?
I'm one of the authors of the XEP and was part of the Google Talk team back in the day. I haven't been working on it in quite a while so I really don't speak for the current team. First off, I'm super proud of these guys finishing off this work. It was a long time coming. As for why we chose XMPP over SIP: The team had made the choice to base the core IM product on XMPP before I joined. That decision was based on the…
And now this news indicates that it appears to be AbandonWare. Which is a real pity.
Earlier quoted context omitted.
What about people who don't like or use the Gmail web UI (I use it over IMAP) but would still like to use Google Talk to stay in touch with friends? Is my only option to use third-party clients? I like Google Talk but dislike Gmail, and tying the two together doesn't really work out in my favour.
"What about people who don't like or use the Gmail web UI" Well there is always http://talkgadget.google.com/talkgadget/client Opening a webbrowser window with that and you are set. No Gmail UI, and you get video chat.
Earlier quoted context omitted.
I'm one of the authors of the XEP and was part of the Google Talk team back in the day. I haven't been working on it in quite a while so I really don't speak for the current team. First off, I'm super proud of these guys finishing off this work. It was a long time coming. As for why we chose XMPP over SIP: The team had made the choice to base the core IM product on XMPP before I joined. That decision was based on the…
I'm curious as to why the windows Google Talk product has stalled - I always thought Google planned to improve it to make it a worthy competitor to Skype, but it seems to have stalled. And now this news indicates that it appears to be AbandonWare. Which is a real pity.
My original email had more details: We are pleased to announce that we have launched support for Jingle XEP-166 and XEP-167 for Google Talk calls to and from Gmail, iGoogle, and Orkut. We have also added the same level of support to libjingle ( http://code.google.com/p/libjingle ), which is used by many native clients. From this point on, it will be our primary signalling protocol, and the old protocol will only rema…
Well, I am not sure why Google went with XMPP when the rest of the telecom and networking industry is gravitating towards IETF SIP as signaling protocol. There are so may overlaps in both of them in the sense that they use the same components such as SDP and ICE. Can anyone from Google or otherwise throw some more light on - Why Google prefers XMPP over SIP - In what areas XMPP is better that SIP I am not stating tha…
I guess SIP has weak support for Instant Messaging, which was the primary use case for Google Talk before video chat came along. On the other hand the Jingle spec [1] contains many references to SIP: "Furthermore, Jingle is not intended to supplant or replace existing Internet technologies based on the Session Initiation Protocol (SIP; RFC 3261). Because dual-stack XMPP+SIP clients are difficult to build, Jingle was…