Thoughts on 0.90

Hi,

I had some free time on my hand (others would say i took a day off from
learning :) so i summarized and looked through what we will need for the
0.90 milestone:


Requirements:

      * Support for more than two SyncDevice per SyncGroup
      * Plugin system for SyncDevicePlugins
      * Communication between SyncDevicePlugins and SyncEngine via RPC
        mechanism (Dbus, XML-RPC, sockets etc)
      * Separation of GUI and SyncEngine. Communication via RPC
        mechanism (Dbus, XML-RPC, sockets etc)
      * Possibility for a single plugin to handle multiple devices
      * Capabilites for the device
      * Conflict resolution based on the SyncType and Capabilities.
        (Overwrite from one side, Merge based on SyncType, Automatic
        merge based on capabilites)
      * Plugin system for SyncTypes
                Contact-Plugin:
                      * Support for converting and spliting names
                      * Support for converting and spliting adresses /
                        labels
                Todo Plugin:
                      * do we need anything here?
                Calendar-Plugin:
                      * Fake / Unfake recurring events if SyncDevice
                        needs it
                No Plugin:
                      * For all SyncEntities which can pass through the
                        SyncEngine untouched
      * Portable


Keyword explanation:

      * SyncDevice: Any device, server, program that will be
        synchronized
      * SyncGroup: Made up of two or more SyncDevices, which are
        supposed to stay synced
      * SyncTypes: Format which are syncable via multisync2 (contacts,
        todos, emails, files etc)
      * SyncEngine: The central methods in multisync2 which provide the
        sync functions
      * GUI: Interface to control the SyncEngine .Could be a real GUI, a
        CLI or some other way (external application or program like
        phpgroupware)
      * Capabilites: A list of values which parts of a SyncType the
        SyncDevice can implement
      * SyncEntity: A single instance of a SyncType (a contact, a file
        etc)

      * SyncStorage: A storage within multisync2 to store SyncEntities
        which are not synced to all SyncDevices yet ???

Can we decide on these keywords so we never happen to talk at
cross-purposes?

Anything to add so far?
I think the most important thing to decide first is what transport to
use (dbus, xmlrpc, sockets, etc). Any thoughts on this one?

Armin





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click