<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Google Data &#187; Sean Egan</title>
	<atom:link href="/author/sean-egan/feed/" rel="self" type="application/rss+xml" />
	<link>https://googledata.org</link>
	<description>Everything Google: News, Products, Services, Content, Culture</description>
	<lastBuildDate>Fri, 03 Apr 2015 21:58:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1.1</generator>
	<item>
		<title>Libjingle 0.3.0</title>
		<link>https://googledata.org/google-talk/libjingle-0-3-0/</link>
		<comments>https://googledata.org/google-talk/libjingle-0-3-0/#comments</comments>
		<pubDate>Thu, 16 Mar 2006 21:56:00 +0000</pubDate>
		<dc:creator><![CDATA[Sean Egan]]></dc:creator>
				<category><![CDATA[Google Talk]]></category>
		<category><![CDATA[g talk]]></category>
		<category><![CDATA[google chat]]></category>
		<category><![CDATA[google im]]></category>
		<category><![CDATA[google messenger]]></category>
		<category><![CDATA[google talk mobile]]></category>
		<category><![CDATA[googletalk]]></category>
		<category><![CDATA[gtalk]]></category>
		<category><![CDATA[gtalk mobile]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[If you're a developer interested in making voice calls compatible with Google Talk, you depend on two separate code components. First, you need an implementation of Google Talk's signaling and peer-to-peer protocol, which is currently being standardize...]]></description>
				<content:encoded><![CDATA[If you're a developer interested in making voice calls compatible with Google Talk, you depend on two separate code components. First, you need an implementation of Google Talk's signaling and peer-to-peer protocol, which is currently being standardized as <a href="http://www.jabber.org/jeps/jep-0166.html">Jingle</a> through the <a href="http://www.jabber.org">  Jabber Software Foundation</a>'s JEP process. In December, we launched <a href="http://code.google.com/apis/talk/index.html">libjingle</a>: the very code Google Talk uses to implement this protocol, distributed as a library for third-party developers. Since this release, we've witnessed a lot of amazing work being done based on this library, and we're very pleased with how it's been received.<br /><br />The second requirement for third-party developers is a set of media componentry. For this task, the Google Talk client chose the high-quality GIPS Voice Engine from <a href="http://www.globalipsound.com">Global IP Sound</a> (GIPS). This Tuesday, GIPS  <a href="http://www.globalipsound.com/newsroom/newsroom.php?newsID=156&tot=105">announced</a> the formation of the <a href="http://developer.globalipsound.com">GIPS Developer Community</a>, which provides a "light" version of GIPS Voice Engine, called Voice Engine Lite. The <a href="http://sourceforge.net/projects/libjingle">libjingle 0.3.0</a> release, which we've just released today, includes optional support for GIPS Voice Engine Lite, so now developers have the choice to combine the high-quality peer-to-peer connections of libjingle with the powerful audio capabilities of GIPS Voice Engine Lite.<br /><br />Sean Egan<br />Software Engineer<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/16882295-114255819118720489?l=googletalk.blogspot.com' alt='' /></div>]]></content:encoded>
			<wfw:commentRss>https://googledata.org/google-talk/libjingle-0-3-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Libjingle 0.2.0</title>
		<link>https://googledata.org/google-talk/libjingle-0-2-0/</link>
		<comments>https://googledata.org/google-talk/libjingle-0-2-0/#comments</comments>
		<pubDate>Wed, 08 Feb 2006 20:10:00 +0000</pubDate>
		<dc:creator><![CDATA[Sean Egan]]></dc:creator>
				<category><![CDATA[Google Talk]]></category>
		<category><![CDATA[g talk]]></category>
		<category><![CDATA[google chat]]></category>
		<category><![CDATA[google im]]></category>
		<category><![CDATA[google messenger]]></category>
		<category><![CDATA[google talk mobile]]></category>
		<category><![CDATA[googletalk]]></category>
		<category><![CDATA[gtalk]]></category>
		<category><![CDATA[gtalk mobile]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[I've released libjingle 0.2.0 to the Sourceforge.net project page. Notable changes in 0.2.0 include build support for Windows using Visual Studio Express, TLS support (this encrypts the communication between applications using libjingle and the server)...]]></description>
				<content:encoded><![CDATA[<span class="q">I've released libjingle 0.2.0 to the Sourceforge.net <a href="http://sourceforge.net/projects/libjingle">project page</a>. Notable changes in 0.2.0 include build support for Windows using Visual Studio Express, TLS support (this encrypts the communication between applications using libjingle and the server), and a new "<a href="http://code.google.com/apis/talk/tunnel_session.html">tunnel</a>" session type. The tunnel session uses what we call "pseudo-tcp" to reliably transfer a TCP-like stream of data over Jingle's peer-to-peer connections. The Libjingle <a href="http://code.google.com/apis/talk/index.html">documentation </a>has also been updated to describe how to use this new session type.<br /><br />Sean Egan<br />Software Engineer<br /></span><span class="q"></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/16882295-113942976768845964?l=googletalk.blogspot.com' alt='' /></div>]]></content:encoded>
			<wfw:commentRss>https://googledata.org/google-talk/libjingle-0-2-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jingle All The Way</title>
		<link>https://googledata.org/google-talk/jingle-all-the-way/</link>
		<comments>https://googledata.org/google-talk/jingle-all-the-way/#comments</comments>
		<pubDate>Thu, 15 Dec 2005 21:34:00 +0000</pubDate>
		<dc:creator><![CDATA[Sean Egan]]></dc:creator>
				<category><![CDATA[Google Talk]]></category>
		<category><![CDATA[g talk]]></category>
		<category><![CDATA[google chat]]></category>
		<category><![CDATA[google im]]></category>
		<category><![CDATA[google messenger]]></category>
		<category><![CDATA[google talk mobile]]></category>
		<category><![CDATA[googletalk]]></category>
		<category><![CDATA[gtalk]]></category>
		<category><![CDATA[gtalk mobile]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[For me, the most exciting thing about working on Google Talk is having the opportunity to help develop an instant messaging network based on open standards. By using XMPP, an open standard protocol, we give Google Talk users the choice of what client t...]]></description>
				<content:encoded><![CDATA[For me, the most exciting thing about working on Google Talk is having the opportunity to help develop an instant messaging network based on open standards. By using <a href="http://www.jabber.org/">XMPP</a>, an open standard protocol, we give Google Talk users the choice of what client to use, and make it easy for developers to implement their own clients and innovative services on top of our network. From day one, everyone has been encouraged to connect to the service with any <a href="http://www.google.com/talk/otherclients.html">XMPP-capable client</a> they choose.<br /><br />Today, two major advances have been made in the openness of our voice capabilities. This morning, the Jabber Software Foundation (JSF) introduced two new proposed extensions to XMPP, known as <a href="http://www.jabber.org/jeps/jep-0166.html">Jingle</a> and <a href="http://www.jabber.org/jeps/jep-0167.html">Jingle Audio</a>. These enhancements describe how to write software compatible with Google Talk's voice features and have been introduced into the JSF's <a href="http://www.jabber.org/jeps/jep-0001.html">standards process</a> where they'll be reviewed and improved by the XMPP community. To make implementing these extensions even easier, we've released a library we call "libjingle."<br /><br /><a href="http://code.google.com/apis/talk/index.html">Libjingle</a> is the very same code Google Talk uses to negotiate, establish, and maintain peer-to-peer voice sessions, packaged as a <a href="http://www.sourceforge.net/projects/libjingle">library</a> for other developers to use in their own projects. By incorporating Libjingle into your project, you enable its users to voice chat with other users of the Google Talk service.<br /><br />I'm really thrilled to be able to release this source code to the IM development community. This holiday season, it's Jingle all the way!<br /><br />Sean Egan<br />Software Engineer<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/16882295-113468247928558853?l=googletalk.blogspot.com' alt='' /></div>]]></content:encoded>
			<wfw:commentRss>https://googledata.org/google-talk/jingle-all-the-way/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
