next up previous
Next: Reliability and Fault-tolerance Up: How RCDS Achieves its Previous: How RCDS Achieves its

Ease of Deployment

Deployment of RCDS requires no new infrastructure other than that which can be provided directly by existing publishers. Clients, information providers, and mirror servers can each begin supporting RCDS independently of one another, except that ``official'' mirror servers need to obtain credentials in order to add location information to the resource owner's RCDS server.

Clients. A user must have an RCDS aware client in order to benefit directly from RCDS. Such a client may be either a web browser which has RCDS support built-in, or a web proxy which serves as an intermediary between the client and the rest of the Web, using RCDS whenever available. Information providers. In order to support RCDS, an information provider must install (preferably multiple) RCDS servers, register the locations of those servers in the Domain Name System (DNS), and update those servers when resources are changed or new locations are added. The RCDS and DNS servers are freely available. The publisher must also arrange to update the RCDS servers when a resource is changed. Mirror servers. Many resources today are replicated, or mirrored, from their original server. RCDS clients can find such replicas automatically if the original server supports RCDS, and the mirror server updates the appropriate RCDS server whenever it creates or deletes a replica. We have modified some commonly-used mirroring tools to perform this function, and we are developing a new high-performance replication tool. Mirror servers do need permission (and authentication credentials) to add their locations to an RCDS server.

Keith Moore
Fri Feb 7 11:53:58 EST 1997