GrpcStatus

Defines the status of an operation by providing a standard GrpcStatusCode in conjunction with an optional descriptive message.

For clients, every remote call will return a status on completion. In the case of errors this status may be propagated to blocking stubs as a RuntimeException or to a listener as an explicit parameter.

Similarly, servers can report a status by throwing GrpcStatusException or by passing the status to a callback.

Utility functions are provided to convert a status to an exception and to extract them back out.

Extended descriptions, including a list of codes that shouldn't be generated by the library, can be found at doc/statuscodes.md

Defines the status of an operation by providing a standard GrpcStatusCode in conjunction with an optional descriptive message.

For clients, every remote call will return a status on completion. In the case of errors this status may be propagated to blocking stubs as a RuntimeException or to a listener as an explicit parameter.

Similarly, servers can report a status by throwing GrpcStatusException or by passing the status to a callback.

Utility functions are provided to convert a status to an exception and to extract them back out.

Extended descriptions, including a list of codes that shouldn't be generated by the library, can be found at doc/statuscodes.md

Defines the status of an operation by providing a standard GrpcStatusCode in conjunction with an optional descriptive message.

For clients, every remote call will return a status on completion. In the case of errors this status may be propagated to blocking stubs as a RuntimeException or to a listener as an explicit parameter.

Similarly, servers can report a status by throwing GrpcStatusException or by passing the status to a callback.

Utility functions are provided to convert a status to an exception and to extract them back out.

Extended descriptions, including a list of codes that shouldn't be generated by the library, can be found at doc/statuscodes.md