On Sun, 2003-11-30 at 13:28, Tim Müller wrote:
On Sunday 30 November 2003 19:04, Rodrigo Moya wrote:
[snip]
you might want to look at libgnetwork (http://ftp.gnome.org/pub/GNOME/sources/libgnetwork/), which is a GObject-based library for networking. Since it uses GObject, it integrates perfectly with your GTK app. The only problem is that it needs Glib 2.0 (used by GTK 2.0), so you might have to upgrade to GTK 2.0.Pitty with libgnetwork is that (from what I've heard at least) it doesn't even attempt to target the win32 platform as well, which IMHO makes it a lot less ueful for Gtk applications where a win32 port is always a possibly at some point (as opposed to most gnome apps). The GObject-based libgnetwork interface looks pretty neat though - and for a *nix-only app I'd definitively go and use that. Also, gnet is a bit weak on the side of error reporting (it will only tell you that something went wrong, but never what went wrong). Cheers -Tim
The only technical issue I'm aware of (besides the standard system call
differences) with Win32/libgnetwork is GConf for proxy settings. All the
proxy settings stuff is contained in libgnetwork/gnetwork-tcp-proxy.c,
and none of the lowlevel settings-retrieval API stuff is public at all.
Therefore, the only thing keeping libgnetwork from working on windows is
someone to work on libgnetwork for windows :-).
Since we've got a few days left of API/ABI instability, I'll rename the
"socket-fd" properties to "socket", and make
GNetworkTcpServerCreationData an opaque structure. Those are the only
places where Unix-specific stuff is exposed in the API, so I can fix
that up quick enough.
--
Peace,
Jim Cape
http://ignore-your.tv
"It is literally true that, like Christianity, Socialism
has conquered the world by defeating itself."
-- Alexander Berkman, ABC of Anarchism
Attachment:
signature.asc
Description: This is a digitally signed message part