[Opensync-users] IPC branch merged: request for testing

[Eduardo P. H. <eha...@ra...>]

Hi, all,

I've just merged /branches/ipc-branch to trunk on the Subversion
repository. This means that the IPC-mode code[1] will be available in
a test release soon.

This also means that people that will get code from SVN trunk from now
on will use the new IPC-mode code. We invite people to test this code,
and report any problems you have (preferably using the ticket system
on www.opensync.org [2]).

In case you wonder what is the "IPC-mode code": it is an implementation
of the ability to run the plugins as independent process from the
engine. The engine and the plugin processes communicate exchanging
messages. From the IPC overview page[1]:

> There are several reasons for using IPC:=20
>  * Some plugins can only be synchronized if they own the process. Examples
>    for this are evo 1.4, kde and mozilla/thunderbird/sunbird=20
>  * By using and IPC we can circumvent licensing problems if a commercial
>    plugin and GPL plugin would be used at the same time=20
>  * There might be use cases where a IPC is needed (for example if the
>    member is on a different pc)


The new code will also allow you to use the opensync branch of
Kitchensync[3] with the kdepim plugin. Without the IPC code, there were
integration problems in the KApplication main loop handling by both
kitchensync and the plugin. Testing of synchronization using kitchensync
is welcome, too. Please report bugs in the opensync-enabled Kitchensync
branch through www.opensync.org also, instead of bugs.kde.org.

References:

 [1] http://www.opensync.org/wiki/IPC
 [2] http://www.opensync.org/newticket
 [3] http://www.opensync.org/wiki/kitchensync

Regards,

--=20
Eduardo