<?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" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" > <channel><title>Comments on: Google&#8217;s CalDAV &#8211; Not quite the perfect solution</title> <atom:link href="http://blog.gruby.com/2008/12/02/googles-caldav-not-quite-the-perfect-solution/feed/" rel="self" type="application/rss+xml" /><link>http://blog.gruby.com/2008/12/02/googles-caldav-not-quite-the-perfect-solution/</link> <description>Another semi-useless spot on the web...</description> <lastBuildDate>Mon, 30 Jan 2012 07:45:23 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Scott Gruby</title><link>http://blog.gruby.com/2008/12/02/googles-caldav-not-quite-the-perfect-solution/comment-page-1/#comment-12970</link> <dc:creator>Scott Gruby</dc:creator> <pubDate>Thu, 04 Dec 2008 05:04:40 +0000</pubDate> <guid isPermaLink="false">http://blog.gruby.com/?p=1981#comment-12970</guid> <description>Apple needs to step up to the plate and deliver a full solution soon as this current situation almost makes it impossible to deploy an Apple calendaring solution in the enterprise. Even if Snow Leopard gets closer to fixing this, this really doesn&#039;t help much as it will take years for Snow Leopard to get deployed in companies. I&#039;m currently dealing with a mix of Tiger and Leopard users so already I have to figure out how to deal with non-CalDAV compatible iCal.</description> <content:encoded><![CDATA[<p>Apple needs to step up to the plate and deliver a full solution soon as this current situation almost makes it impossible to deploy an Apple calendaring solution in the enterprise. Even if Snow Leopard gets closer to fixing this, this really doesn't help much as it will take years for Snow Leopard to get deployed in companies. I'm currently dealing with a mix of Tiger and Leopard users so already I have to figure out how to deal with non-CalDAV compatible iCal.</p> ]]></content:encoded> </item> <item><title>By: Brian M. Criscuolo</title><link>http://blog.gruby.com/2008/12/02/googles-caldav-not-quite-the-perfect-solution/comment-page-1/#comment-12969</link> <dc:creator>Brian M. Criscuolo</dc:creator> <pubDate>Wed, 03 Dec 2008 14:09:56 +0000</pubDate> <guid isPermaLink="false">http://blog.gruby.com/?p=1981#comment-12969</guid> <description>The issue with CalDAV and sync is a fundamental design decision by Apple - to not allow non-CalDAV data sources to modify the server data. It can only be done by a CalDAV client.This makes your wish of adding a meeting request to a CalDAV calendar impossible at this time, until you start receiving those requests directly from a server and not from standard iCal invites.It will be interesting to see Apple bring CalDAV full circle, especially since Google is supporting the standard now. They&#039;re going to have to rev the iPhone&#039;s calendar support quite heavily to accomodate this.</description> <content:encoded><![CDATA[<p>The issue with CalDAV and sync is a fundamental design decision by Apple - to not allow non-CalDAV data sources to modify the server data. It can only be done by a CalDAV client.</p><p>This makes your wish of adding a meeting request to a CalDAV calendar impossible at this time, until you start receiving those requests directly from a server and not from standard iCal invites.</p><p>It will be interesting to see Apple bring CalDAV full circle, especially since Google is supporting the standard now. They're going to have to rev the iPhone's calendar support quite heavily to accomodate this.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: blog.gruby.com @ 2012-02-10 11:54:48 by W3 Total Cache -->
