Using specific exception types instead of generic ClientException in case of error

[stschuh]

The CronetException caught onFailed is converted to a ClientException (exception.ToString) without additional information. Would be great to use more specific types (based on ClientException to avoid breaking existing code) with additional information, such as error code, internal error code (without having the need of parsing the error message).

[brianquinlan]

Good suggestion.

CronetException class doesn't have information associated with it other than the message. But its subclasses do.

It would make sense to decode them in the onFailed handler.

[stschuh]

@brianquinlan - exactly. Didn't mention that, but e.g. NetworkException contains additional information (error code, internal error code) that could be exposed, which makes it easier for error handling.