Changing the Reliability Interval within an Application Program

Application programs can override both the factory default and the daemon’s -reliability parameter. An API call can request reliability on a specific service. Any transport can request a reliability interval. The daemon uses the requested value as one of several inputs when it computes the effective reliability interval (see below).

Each request pertains to an individual transport, and is independent of other transports on the service or within an application process. A transport that does not request a specific reliability interval implicitly requests the daemon’s governing value.

Programs can request reliability only from daemons of release 8.2 or later.

An application can request a shorter retention time than the value that governs the daemon as a whole (either the factory default or the daemons -reliability parameter). The daemon silently overrides calls that request a retention time longer than the daemon’s governing value.