|
From: Henrik /K. <he...@ka...> - 2009-10-24 12:56:47
|
Daniel Gollub wrote: > On Friday 23 October 2009 09:05:24 pm Henrik /KaarPoSoft wrote: > > Please only write OpenSync application using the API. > ACK. > >> 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. >> > > You mean something like a daemon? > Yes! > I also had this idea - but i'm not the person going to write that daemon. I > have enough responisbilities to complete the OpenSync API - which a daemon > could base on. > > ACK. But somebody else might write it... >> 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 ??? >> > [...] > > Yeah, i would also use D-Bus for that - i started with a Proof of concept > several years ago. But again, i'm going to concentrate on the OpenSync API > first. > > http://opensync.org/browser/branches/MobileStation?rev=2233 > > I'm fine with the idea people using a Sync-daemon or write a standalone Sync- > application - as long as it's based on OpenSync API ;) > ACK. /Henrik |