id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
1006	Handle parent/child relations between changes	dgollub	dgollub	"Handle parent/child relations between changes. One example parent/child relation is for iCalendar records with ''detached recurrence rules''. For more information see http://www.estamos.de/blog/2008/06/30/icalendar-20-detached-recurrences/

The engine and the format-plugin interface should be aware of parent/child relations and honor that commits to peers should be done in a specific order - .e.g. first parents, then childs.

Implementation ideas:
 * Introduce new format-plugin function to determine child/parent-role
   * This could be a function which returns following enum:
     * OSYNC_CHANGE_RELATION_UNKNOWN
     * OSYNC_CHANGE_RELATION_CHILD
     * OSYNC_CHANGE_RELATION_PARENT
   * The format-plugin should identify on the native format if this is a child
 * extend OSyncObjFormat with a method to call child/parent-role format-plugin function
 * introduce OSyncChange method which calls the OSyncObjFormat child/parent role-method
 * sort parent entries in the OSyncSinkEngine entries list to the beginning
 * sort child entries in the OSyncSinkEngine entries list on the end"	enhancement	new	normal		OpenSync	0.38	normal