A vendor can use the non-transparent Redundancyfeatures to create a Serverproxy running on the Clientmachine to provide transparent Redundancyto the Client. This reduces the amount of functionality that needs to be designed into the Clientand to enable simpler Clientsto take advantage of non-transparent Redundancy. The Serverproxy simply duplicates Subscriptionsand modifications to Subscriptions, by passing the calls on to both Servers, but only enabling publishing and sampling on one Server. When the proxy detects a failure, it enables publishing and/or sampling on the backup Server, just as the Clientwould if it were a Redundancyaware Client.

Figure 33shows the Serverproxy used to provide transparent Redundancy.


Figure 33– Server proxy for Redundancy