powered by Jive Software

Next week''s live chat: Rod Chavez from Google Talk

Hey all,

I’‘m pleased to announce that Rod Chavez from Google Talk will be joining us as a special guest for next week’'s group chat (http://www.jivesoftware.org/group-chat.jsp).

About Rod:


Rod Chavez, Engineering Manager, Google

Rod has been working in software engineering for over 15 years at a variety of companies, among them Borland International, Microsoft, BEA Systems and now Google. Always on the developer side of things, he’'s helped ship Paradox for Windows, dBase for Windows, IE4, IE5, WebLogic Workshop 7.0 and 8.1 and now Google Talk.

When not at work he enjoys a sunny round of golf, a cut-throat game of poker and a fine bottle of wine. Not necessarily in that order.


As per the usual special guest process, please post questions for Rod as messages in this thread. We’'ll use those questions to seed the conversation.

Personally, I’‘m excited for the chat and will try to glean some scalability tips from the Google Talk deploy to assit with Project Pampero: http://www.jivesoftware.org/community/entry.jspa?categoryID=17&externalID=422. I’'ll make another post with my own list of questions in a bit…

Regards,

Matt

Cant figure out any good question. But sounds exiting Will be there, i think.

Oops, it’‘s my birthday on that day But i think i’'kk find some spare hour to chat

Now really wroot, you DO want all your buddies to chime in with a well rehearsed very OFFkey round of “Happy Birthday” don’'t you??

not at all, i dont really like birthdays much, so i’'ll come with other nickname :stuck_out_tongue:

But we’‘ll know it’‘s you by the pointed and knowledgeable questions and insightful commentary. You can’'t hide

I’'m curious to know the following:

  • How long has Google been working on Google Talk? Was it written from scratch?

  • Did you look at using SIP/SIMPLE for Google Talk instead of Jabber/XMPP? If so, why did you decide to go with XMPP?

  • What sort of technologies, programming language(s), operating systems (I suppose this is a no-brainer ), database(?), etc., are being used for Google Talk?

I think that’'s it for now…

Thanks,

Ryan

Here’'s a couple:

Will Google Talk evolve to a more-or-less standard instant messaging application, or can we expect more exotic features to be added? If so, can you give us some hints what those features would include?

Were there specific features that have been discussed but rejected? Which features where that, and why were they rejected?

Hi Rod,

Welcome to the Jabber community! We were very pleased to hear that Google plans “to support open server-to-server federation.” We also understand the importance of having safeguards in place for blocking Spam over IM (SpIM).

(http://www.google.com/talk/developer.html#service_4)

Since Google’'s announcement the JSF has published its first two anti-spim protocols (http://www.jabber.org/jeps/jep-0158.html and

http://www.jabber.org/jeps/jep-0159.html). More proposals are in the works (e.g., a standard way for entities to report sources of spim to each other). During this experimental stage, we’'d really like to have some input (or at least some feedback) from people at Google.

IMHO it will be important to get all client and server developers working in the same direction. Can you tell us how Google is currently intending to combat spim from networks of ‘‘zombie’’ servers once it switches on open server-to-server federation?

Thanks,

  • Ian

Google chose to implement a simple proprietary XMPP voice call setup instead of using TINS (http://www.jabber.org/jeps/jep-0111.html). Do you see issues with TINS, or might Google implement TINS in a future version of its client?

Thanks,

  • Ian

Google chose to implement a simple proprietary XMPP

voice call setup instead of using TINS

(http://www.jabber.org/jeps/jep-0111.html). Do you

see issues with TINS, or might Google implement TINS

in a future version of its client?

I wanted to suggest exactly the same question! :o)

Other things:

I just hope that JiveSoftware would have working s2s at this time, because in other case talking about s2s would looks like conversation of two blind men talking about colors.

I don’'t think that XMPP was designed to accessing webchats. Main feature is s2s, point.

/i

Great! it’'s working now. Normally working MUC would be the next great thing :)(I mean clonning when exit/enter a room)

Finally getting around to posting my questions:

  • What can you tell us about the back-end architecture of Google Talk?

  • Are there any architecture challenges that specifically relate to XMPP?

  • What led Google to choose XMPP vs. SIMPLE, for example?

Regards,

Matt

  • What can you tell us about the back-end

architecture of Google Talk?

you wish

Another question: What is the status of s2s support? Gizmoproject seems to be faster with it than Google …

http://www.jivesoftware.org/group-chat.jsp

Room names:

google1@conference.jivesoftware.org – moderated, read-only room.

google2@conference.jivesoftware.org – open room.

Seems to be a typo, since jivesoftware.org doesn’'t work as an alias server for jivesoftware.com and only the latter one responds.