An OpenSync process ???

[Henrik /KaarPoSoft-2]

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

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

[Daniel Gollub-3]

On Friday 23 October 2009 09:05:24 pm Henrik /KaarPoSoft wrote:
> 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).

JFYI, osynctool is just an implementation reference. In long-term i don't want
to see any application being dependend on osynctool. Also i don't want to see
any non-developer using osynctool.

Please only write OpenSync application using the API.

>
> 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?
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.

>
> 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 ;)

Best Regards,
Daniel


--
Daniel Gollub                        Geschaeftsfuehrer: Ralph Dehner
FOSS Developer                       Unternehmenssitz:  Vohburg
B1 Systems GmbH                      Amtsgericht:       Ingolstadt
Mobil: [phone]         Handelsregister:   HRB 3537
EMail: gollub@...          http://www.b1-systems.de

Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg
http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

[Henrik /KaarPoSoft-2]

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

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel