|
From: Henrik /K. <he...@ka...> - 2009-10-23 19:05:39
|
Currently there seems to be two ways if you want to be the master of OpenSync synchronization: (1) Use osynctool (2) Implement your own master which would call osync_engine_synchronize_and_block (after some osync_engine_set_XXX_callback calls). In a case like blueZync, it would be preferable if there was a running instance of an osynctool-like process, which would accept messages on a socket from blueZync to create a group, discover, sync, whatever. This way blueZync - an extension to Mozilla Thunderbird - could be kept a portable JavaScipt extension communicating with "the opensync process" through sockets. This way we would have no difficult-to-port C code in blueZync, and no need for an end-user to install anything but a native OpenSync (with this "new" process) and a platform-independent plugin to Thunderbird. Any comments on that? I am also thinking about dbus, but since I do not know the details of dbus, I don't know if would be useful. How about an OpenSync service on dbus ??? /Henrik |