Re: [Opensync-users] collaboration proposal

[Michael B. <mic...@cm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Brian,

Brian Cavagnolo wrote:
> 
> Wind River has been evaluating libsyncml, and we're happy with the 
> results so
> far.  We'd like to collaborate to move some of our changes upstream.  
> Also, we
> have some other developments in mind that we'd also like to
> discuss/collaborate/contribuite.  I've listed the rough areas in which the
> changes fall.  Please comment if these changes sound useful, reasonable, 
> etc.:

The simple answer is a big YES to all points. I only comment the points
where I have more to say then only yes ;)

> 3. Split the ENABLE_HTTP functionality into two parts: 
> ENABLE_HTTP_CLIENT and
> ENABLE_HTTP_SERVER.  This will allow only building the required half.

Do you need this because of your different libraries for the client and
server part?

> 4. Develop alternative HTTP client that does not depend on libsoup.  (We're
> using libcurl instead).  We'd like to avoid depending on libsoup and the
> portions of glib required to support it.

Which portions of the glib do you mean? libsoup is problematic for me
because of the poor SSL/TLS support. The upcoming libsyncml 0.6.0 stuff
(please see trunk) makes heavy use of the glib.

> 6. Migrate away from the heavy polling to a more event-driven model.

Definitely a long term wish from me.

So you are more than welcome. I hope you can split your patches into
small parts. This would make it possible for me or/and you to port them
to the new trunk.

Best regards

Michael

P.S. BTW we have a developer list.
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksNDIIACgkQ2L0ZGCAwWqtNnwCg1HjbX6juR+Qf6VnHl0RG0RX2
6HYAn3uNQJyhau2zt5XVLIR+1WAv0fwT
=FLrl
-----END PGP SIGNATURE-----