opensync-users

[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

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

[matthias j. <jah...@fr...>]

Am Sonntag, 9. Juli 2006 16:28 schrieb Eduardo Pereira Habkost:
> 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]).

The Debian and ubuntu repro (http://www.in.fh-merseburg.de/~jahn/) contains=
=20
now current packages of opensync (ipc merge) and kitchensync-opensync for=20
Debian:
	- unstable (sid)=20
	- testing (etch)
	- stable (sarge)
and Ubuntu Dapper.

Happy testing

Matthias=20

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

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

Hi,

There was a annoying bug in the code that made the synchronization hang
in the initialization if there were old pipe files inside the member
directories in ~/.opensync. Sorry for letting this go through. I've just
committed a fix to this (revision 1101).

Another known issue: The support for 'msynctool --wait' (needed
syncml-http-server) isn't complete yet.

On Sun, Jul 09, 2006 at 11:28:24AM -0300, Eduardo Pereira Habkost wrote:
> Hi, all,
>=20
> 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.
>=20

--=20
Eduardo

[Opensync-users] msynctool --wait working again on trunk

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

Hi,

(if you are not using the recent code from the trunk on the svn
repository, where the ipc-branch code was recently merged, you
don't need to worry about this message)

(Anyway, if you are not using the current code from svn trunk yet but
are interested in helping to test it, your help would be very welcome :)

The most annoying bug (for people using syncml-http-server plugin) in the
recently-merged IPC code was just fixed. 'msynctool --wait' wasn't working
in the new code yet, because sync alerts weren't being handled by
osplugin.

I've just added the code for this on svn trunk. It is working when using
file-sync and the sync alert generated by monitoring the directory.
Unfortunately I couldn't test it using syncml-http-server, right now,
but it is supposed to work with syncml-http-server and other plugins
that support sync alerts.

Please let me know (preferably through the bug reporting on
www.opensync.org, but you can mail me if you like) if you still have
any problems with the new code.

Regards,

-- 
Eduardo