D16299: fallback to dnssd service discovery if smb listDir failed on root

[Andrew Crouthamel]

acrouthamel added a comment.


  In D16299#363498 <https://phabricator.kde.org/D16299#363498>, @sitter wrote:
  
  > If someone has a thought to offer on this please do.
  >  Personally I am somewhat leaning towards assuming that systems should be properly configured. The problem with setting the URL to the ip address is that it messes with the visual look in the address bar. So, if we want reliable resolution and good looks we'd need to resolve each dnssd address (e.g. `foobar.local`) to their ip address (e.g. 172.17.0.1) via kdnssd and then resolve that back to a hostname via glibc/qhostinfo (e.g. `foobar.sky.net`). That way we'd know that the name we have in the end is in fact resolvable by the system without aid from dnssd. Speed impact of this aside it also adds 3 additional points of failure (and KDNSSD currently doesn't implement the resolver API it seems).
  
  
  I would recommend assuming DNS and systems are configured properly. I say that as someone with ~15 years IT experience. Modern IT networks are so heavily reliant on it (ever set up a VMware cluster? phew!), almost nothing works if it is not set up properly.

REPOSITORY
  R320 KIO Extras

REVISION DETAIL
  https://phabricator.kde.org/D16299

To: sitter, #frameworks, #dolphin
Cc: acrouthamel, alexde, bcooksley, ngraham, kde-frameworks-devel, kfm-devel, sourabhboss, feverfew, michaelh, spoorun, navarromorales, firef, andrebarros, bruns, emmanuelp, mikesomov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20181121/3eec7c27/attachment.html>