Service Reliability Rule

Client transport objects that connect to the same daemon could specify different reliability intervals on the same service—whether by requesting a reliability value, or by using the daemon’s governing value. In this situation, the daemon resolves the difference using a method that favors more stringent reliability requirements, yet limits the maximum value to the daemon’s governing value.

Procedure 

1.

The daemon begins by selecting the largest potential value from among all the transports on that service.

2.

The daemon then compares that maximum value to the daemon’s governing value, and uses the smaller of the two as the effective reliability interval for the service (that is, for all the transports on the service). That is, the daemon’s governing value limits the maximum requested value.

Contrast this rule with the Lower Value Rule that applies between two daemons; see above.

Service Reliability Rule

Consider a situation in which the daemon’s command line specifies 40 seconds as the -reliability time value. Two client transports on service 7500 request reliability values of 30 seconds and 50 seconds. The daemon selects the largest value, 50, and then limits it to the daemon’s governing value of 40 seconds.

Now consider a separate situation, in which the daemon uses the factory default reliability (60 seconds) as its governing value. A client transport requests 75 seconds. The daemon limits that request to 60 seconds.