API Architecture

Establish and manage a connection to the browser administration interface of a daemon process.

This interface defines methods common to all Rendezvous components.

The DaemonManager automatically creates a proxy instance, which the program uses as its main interface to the daemon process.

These interfaces define methods specific to each Rendezvous component. For example, RvrdProxy defines methods for interacting with rvrd.

Each proxy interface represents one aspect of the behavior of the component. Some components incorporate several aspects, and they support the corresponding proxy interfaces. For example, rvrd has aspects of communications daemon (rvd) behavior, and aspects of routing daemon behavior (rvrd)—so it supports both RvdProxy and RvrdProxy.

Programs cast the proxy instance to the appropriate proxy interfaces in order to call methods specific to the corresponding aspects.

These classes represent data structures within a communications daemon process (including rvd, rvsd, rvrd and rvsrd).

These classes represent data structures within a routing daemon process (including rvrd and rvsrd).

This class represents a data structure that can contain an X.509 certificate. These slots occur in processes that permit secure HTTPS connections (including rvd, rvsd, rvrd, rvsrd, and rvcache).

These classes represent data structures within a secure daemon process (including rvsd and rvsrd).

These classes represent data structures within an rvcache process.

These classes structure general information from the various components.

These classes structure parameter information from the various components.