[systemd-devel] [PATCH 00/28] Initial DHCP v4 library implementation

[Marcel Holtmann]

Hi Colin,

>> that is the long term plan. Once ConnMan is switching over to use libsystemd-bus and kdbus,
>> we are switching over to using the systemd event loop instead of GLib main loop 
> 
> But I think the long term architecturally correct place for the core
> system main loop is glibc, not systemd.
> 
> For example, that would allow runtimes like OpenJDK and Python to
> unconditionally depend on it (if present).
> 
> As systemd's event loop becomes public API, it has the potential to
> create interoperability problems for GNOME - think applications like 
> https://git.gnome.org/browse/gnome-logs
> that want to both monitor the systemd journal and talk to GTK+.
> 
> At the moment it's OK because sd_journal has APIs sufficient to plug in
> external loops.
> 
> Adding a mainloop API to glibc would be a lot of work - it might even
> entail trying to get it by POSIX.  At least it'd entail describing the
> interaction with the other POSIX APIs.  But I think that'd be worth the
> effort.

I am a bit lost on your concerns here. Our focus for ConnMan is libsystemd-bus and kdbus support. Over time we will be removing our dependency on GLib completely. So the systemd event loop will become our only event loop.

And as a system daemon, I only care about writing to the Journal. No idea why I would need a event loop for that.

Regards

Marcel