<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Google Contacts API bug 2649</title>
	<atom:link href="http://www.zindus.com/blog/2011/07/05/google-contacts-api-bug-2649/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zindus.com/blog/2011/07/05/google-contacts-api-bug-2649/</link>
	<description>Google and Zimbra contact sync for Thunderbird.</description>
	<pubDate>Thu, 17 May 2012 10:13:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: ZE</title>
		<link>http://www.zindus.com/blog/2011/07/05/google-contacts-api-bug-2649/#comment-1796</link>
		<dc:creator>ZE</dc:creator>
		<pubDate>Sun, 16 Oct 2011 16:15:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.zindus.com/blog/?p=128#comment-1796</guid>
		<description>From the July 8, 2011 comment in the bug tracker:
"What it means is that the photo your application is requesting might have been coming from an upload made before the fix on write requests."

This suggests that it ought to work on a "go-forward" basis for new data.  Based on this, does it make sense to allow the sync as an option in Zindus?</description>
		<content:encoded><![CDATA[<p>From the July 8, 2011 comment in the bug tracker:<br />
&#8220;What it means is that the photo your application is requesting might have been coming from an upload made before the fix on write requests.&#8221;</p>
<p>This suggests that it ought to work on a &#8220;go-forward&#8221; basis for new data.  Based on this, does it make sense to allow the sync as an option in Zindus?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

