Hello systemd, We are closely observing the varlink development and excited about it. Our guys who were at the all systems go conference mentioned that the Resolver is not part of the systemd family. Ref: Resolver (https://varlink.org/) . What is the upstream’s thoughts regarding service discovery?
>From the NEWS: “systemd-machined gained a pretty complete set of Varlink APIs exposing its functionality. This is an alternative to the pre-existing D-Bus interface.” For example, how can systemd-machined be discovered? If the varlink interface is an alternative to the D-Bus, how is the authorization handled? The JSON transcoding is great for debugging but it is consuming CPU cycles in production, especially important for constraint devices. Has there been any discussion on using alternative transcoding but switching to JSON with monitor connections. I think it would be great to know systemd’s roadmap around varlink. Thank you for your time Umut
