Hi,

is there a reason, why the Zeroconf plugin is based on Avahi instead of the classes in the DNSSD namespace?

The problem is that kdelibs depends on Apple's Zeroconf implementation mDNSResponder and Avahi and mDNSRepsonder can't coexist. That's the reason why the Zeroconf plugin is disabled in the FreeBSD port.

Looking at the classes in the DNSSD namespace it seems incredibly easy to add Zeroconf support using them (look e.g. at how kftpgrabber implements Zeroconf support). So, why Avahi?

Thanks,

Markus

It was developed by a couple of students as a school project. They chose avahi, we just integrated the plugin.

We will probably move to KDE dnssd classes in the future, but we have other things to do at the moment.

The plugin was originally designed as a school project by authors signed in the sources. They chose Avahi, don't ask me why. I'm not very familiar with the stuff...

Ah, great! Thanks for the clarification.

Markus

how it works?

Just for peoples info - the new kDNSSD (as of KDE 4) can use either the mDNSResponder or Avahi as its backend. This makes it better for cross platform implementation as well if(when) we move to kDNSSD.

how it works?

For Apples sales pitch on zeroconf see:
http://www.apple.com/macosx/technology/bonjour.html
For more technical info see:
http://www.zeroconf.org