replacing libsoup with nanohttp?

[Santtu Lakkala]

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

Jussi Kukkonen wrote:
> I have no problems with using libsoup for fetching data over http,
> except that it and some of its depependencies are not included on
> maemo... I know this is not a very good reason to change things, so if
> there was any reason for choosing this specific http lib I'll just live
> with the current situation.

I would imagine the reason behind libsoup is the GLib-based API. It was
at least the reason why I chose it (or changed to it) in maemo-blog.
xmlrpc-c (using curl) didn't integrate too nicely with GMainLoops,
especially the asynchronous stuff was hackish.

At least the async stuff using gmainloops was trivial with libsoup,
whether this applies here obviously depends on if you actually need
asynchronous transfers.

> Otherwise I might be tempted to change to using nanohttp, which is
> included in libxml2 (which is already a dependency for the webservice
> backends).

libxml2 would be already used by gnome, kde and maemo which would make
it less of a burden, obviously. It, however, doesn't seem to be able to
do async stuff (didn't look too far though).

I personally like libsoup (even with the dependencies), but then again I
needed stuff like https, which I guess nanohttp doesn't support. I have
once or twice cursed the fact that it's built with gnutls instead of
openssl, as the latter would be part of ITOSes (I think it's a licensing
issue though, there used to be openssl-support in older libsoups).

- --
Santtu Lakkala
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFGswwSX9Rc0+po4p0RAjeCAJ0YuyNq+2pG4d6TB11R1t7eVtlK5gCgmnea
XJPoqLNC/aKj4m80H7Wt+bk=
=vekU
-----END PGP SIGNATURE-----