Changes between Version 8 and Version 9 of ArchitecturalOverview

Show
Ignore:
Timestamp:
07/18/08 17:25:44 (5 years ago)
Author:
UncleOp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ArchitecturalOverview

    v8 v9  
    88 
    99 * '''libavahi-common''' - a library containing some function used both by clients to the avahi-daemon and the mDNS stack itself. 
    10  * '''libavahi-core''' - A library implementing a flexible mDNS/DNS-SD stack. The most prominent consumer is avahi-daemon. Besides that primarily useful for developers of embedded applications. This stack is very avanced and has some uncommon features like mDNS reflection. A preliminary (doxygen generated) API documentation for this and libavahi-common is [http://avahi.org/download/doxygen/ available.] 
     10 * '''libavahi-core''' - A library implementing a flexible mDNS/DNS-SD stack. The most prominent consumer is avahi-daemon. Besides that primarily useful for developers of embedded applications. This stack is very advanced and has some uncommon features like mDNS reflection. A preliminary (doxygen generated) API documentation for this and libavahi-common is [http://avahi.org/download/doxygen/ available.] 
    1111 * '''libavahi-client''' - A minimal wrapper around the DBUS API to simplify its usage. Hides the DBUS internals completely. This resembles the API of libavahi-core more or less. 
    1212 * '''libavahi-glib''' - An adapter for connection avahi-client or avahi-core to a GLib main loop. 
    1313 * '''libavahi-qt''' - Adapter connecting to Qt 3 or Qt 4 core main loop (two separate versions can be built) 
    14  * '''avahi-discover-standalone''' - A GTK tool for enumerating all available services on the local LAN. Its links directly against libavahi-core, i.e. embedds its own mDNS stack. You should use it only for debugging, since it's not a good idea to run multiple mDNS stacks simultaneously on the same machine. 
     14 * '''avahi-discover-standalone''' - A GTK tool for enumerating all available services on the local LAN. Its links directly against libavahi-core, i.e. embeds its own mDNS stack. You should use it only for debugging, since it's not a good idea to run multiple mDNS stacks simultaneously on the same machine. 
    1515 * '''avahi-daemon''' - The avahi daemon which makes use of libavahi-core to implement an mDNS stack which is accessible by different ways: 
    1616   * System administrators may put short XML fragments in /etc/avahi/services to publish semi-static services (e.g. SSH) 
    17    * A so called "simple protocol" whith a very limited command set which is used exclusively by nss-mdns (to resolve host names via mDNS) and avahi-dnsconfd 
     17   * A so called "simple protocol" with a very limited command set which is used exclusively by nss-mdns (to resolve host names via mDNS) and avahi-dnsconfd 
    1818   * The DBUS interface for normal clients (like nautilus or gaim) which is an IPC wrapper around the functions provided by libavahi-core  
    1919 * '''[http://0pointer.de/lennart/projects/nss-mdns/ nss-mdns]''' - A GNU libc NSS module for host name resolving using mDNS. This is an external project maintained by Lennart and not part of avahi since it doesn't require avahi to be useful. But if it finds a running avahi daemon it makes use of its superior RR cacheing.