-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Apr 01, 2008 at 05:07:31PM +0200, Mathias Hasselmann wrote: [...] > > Personally, I'be rather scared than delighted ;-) > > So in data centers you don't even trust the machines in your broadcast > domain?
Kind of. Put it another way: never have services running you don't use. [...] > > Isn't there a less-intrusive option to linking a lib into each and every > > possible server, like a config file in which to put what is to be announced? > > You could directly talk to the D-Bus interface of Avahi. libavahi-client > just is a convenience wrapper. Well, but this route will be much more > cumbersome. So this goes through the D-Bus. Makes kind of sense. Thanks for the enlightenment. > One other route is calling avahi-publish-service on startup and killing > it on shutdown, but: avahi-publish-service really only exists for > demonstration purposes and doesn't handle service name collisions for > instance. I don't believe that a high-profile application like > Postgresql should rely on low-quality hacks, like invoking educational > demo programs. Unelegant as it might seem -- this solution still affords a lot more when it comes to "separation of concerns". I'm still a bit wary at the prospect that each and every daemon evolves into a huge fuzzball linked to all conceivable service-lets with a multitude of funny side-effects (remember tcpwrappers?). Of course, "you can always disable this at compile time", but let's face it: with the predominance of binary distribs, the path of least resistance will be to put up with whatever strange side-effects. I would really prefer a more loosely coupled system. Regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFH8lYJBcgs9XrR2kYRAmDJAJ4jWKYkhUfKEAIaZVnIbAAEqJF2AwCfS/6D 4rH9OoY7wjia7h1cuk5CjZI= =AF1W -----END PGP SIGNATURE----- -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches