On Fr, 18.10.24 16:27, Petr Menšík (pemensik@xxxxxxxxxx) wrote: > Is there any API description of the Varlink API, which you are referring to? In Varlink introspection contains the documentation itself. i.e. here's what "varlinkctl introspect /run/systemd/resolve/io.systemd.Resolve io.systemd.Resolve" looks like: https://paste.centos.org/view/ef5c1342 It carries some documentation, but it's not complete though. > But yes, we have realized we may need encrypted resolution already in > Anaconda, which makes D-Bus activation quite early. Network Manager needs > it. On the other hand, until you have working some network connectivity, the > only data ready at that time can be provided by nss-files or nss-myhostname > plugin. Other services do not have a way, how to fetch other usable > information at that time. If they can use some plugins without specialized > service, then that service needs to be up only when network is ready at > least partially. networking solutions such as systemd-networkd run during early boot and provide networking super ealry, long before D-Bus or anything else like that. It can run immediately after PID 1 initialized, and it does. > > Dunno. Varlink is a trivial IPC. In systemd-resolved we support it > > side-by-side with D-Bus. I have zero interest in adding a 3rd IPC > > interface, hence whatever you come up with, expect us to be very cool > > on the idea on adding more. > > That sounds like Vendor Lock-in approach. Either you use our protocol or you > are screwed. It's a pretty trivial interface. You are welcome to implement it in any other implementation if you want to. > DBus is common building blocks of GUI applications written in GTK or Qt. But > I haven't seen many server implementations with decent DBus support. If you > would like to observe busy (multi)gigabit link with tcpdump, there might be > a lot of queries coming, per second. DNS itself is a quite efficient binary > protocol, often already implemented in clients relying on it. I trust you > know about D-Bus much more than me and that it can pass binary encoded and > structured information too. But I am not sure whether complete name > resolution history on machine should pass via DBus. In whatever > form. As mentioned before, I doubt D-Bus is the right choice for this. Lennart -- Lennart Poettering, Berlin -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
