OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
The fault_status attribute has the following characteristics:
• Occurs where you do not want transparent local/remote behavior
• Occurs where you expect that you may be passing incorrect data to the server or the
server is not coded robustly, or both
• Works well for fine-grained error handling
• Requires that you adjust procedure declarations between local and distributed code
• Controls the reporting only of errors that come from the server and that are reported
via a fault packet
For more information on the fault_status attribute, see Chapter 18.
16.2.3 The comm_status Attribute
The comm_status attribute requests that RPC communications failures be reported
through a designated status parameter instead of by an exception. The comm_status
attribute has the following characteristics:
• Occurs where you expect communications to fail routinely; for instance, no server is
available, the server has no resources, and so on
• Works well for fine-grained error handling; for example, trying a procedure many
times until it succeeds
• Requires that you adjust procedure declarations between local and distributed code
to add the new status parameter
• Controls the reporting of errors only from RPC runtime error status codes
For more information on the comm_status attribute, see Chapter 18.
16.2.4 Determining Which Method to Use for Handling Exceptions
Some conditions are better for using the comm_status or fault_status attribute on an
operation, rather than the default approach of handling exceptions.
16 − 8 Tandem Computers Incorporated 124245