Crossing Network Boundaries

When a network boundary separates rvcache from its client programs, and a routing daemon (rvrd) connects them across that boundary, you must configure rvrd to ensure correct operation of rvcache.

Cached Subjects

The routing daemons (on both sides of the neighbor link) must permit all the cached subjects to flow from all senders to all rvcache processes.

Query Subjects

The rvrd configuration for exchanging query subjects depends on the distribution of rvcache and its query clients.

•

If each network runs one local cache process, with all the caches synchronized (so they all contain the same data), then it is crucial that only one rvcache process receive each query. The routing daemons must not import or export _SNAP.> (the query subject).

•

If only one network runs a cache process, and programs on other networks query it across the network boundary, then the routing daemons must forward _SNAP.> (the query subject) into the rvcache network. That is, rvrd must import these query names into the rvcache network; rvrd must export these query names from each query client network.