While a managed network (in this context, meaning a larger network with a trained network administrator, albeit perhaps part time) would normally use DHCP to provide IP addresses, and DNS to provide name to address translation, it is possible that some of the features of a zeroconf network can still be effectively employed in managed network.
This is particular evident when considering peering protocols. For example, the Apple iChat system is effectively a local network peer-to-peer instant messenger[1]. The iChat client uses DNS Service Discovery (as discussed previously) to determine which other users are currently running iChat, and presents this as a list. This avoids the need to set up and run a Jabber server, for example.
Similarly, the KDE VNC application (KRFB) can use Service Location Protocol to provide a list of hosts currently providing RFB protocol[2] services. This avoids the need to determine and hand enter a host name or IP address.
| [1] | For completeness, it should be noted that this is not the only capability in the iChat application. For example, iChat can also be used as an AIM client. In this example, the "Rendezvous" mode is being discussed. |
| [2] | The protocol is really called RFB. VNC is the name of functionality provided by applications that used RFB. |
| <<< Previous | Home | Next >>> |
| Zeroconf in the home | The case against Zeroconf |