<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>Allow SyncML conflict resolution by duplication</title>
  <pubDate>Thu, 21 Aug 2008 19:31:29 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/6657</link>
  <atom:link rel="self" type="application/rss+xml" title="Allow SyncML conflict resolution by duplication" href="http://bugs.horde.org/ticket/6657/rss" />
  <description>Allow SyncML conflict resolution by duplication</description>

  
  
  <item>
   <title>The SyncML module in Horde responds to a conflict situation </title>
   <description>The SyncML module in Horde responds to a conflict situation (item edited on both the server and the client since the last synchronization) with &quot;first synchronization wins&quot;. This means the client will usually overwrite any modifications done on the server as the client usually synchs first during a synchronization run.

The attached patch will respond to such conflicts with a duplication of the conflicting element. I believe this is preferable over possible data loss. If necessary it could also be made configurable.</description>
   <pubDate>Mon, 28 Apr 2008 03:56:56 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6657#t44966</link>
  </item>
  <item>
   <title>Updated patch to current CVS HEAD. </title>
   <description>Updated patch to current CVS HEAD. </description>
   <pubDate>Wed, 07 May 2008 09:22:37 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6657#t45194</link>
  </item>
  

 </channel>
</rss>
