处理API错误与网络错误(Handling API errors vs Network errors)

 我正在构建SDK。 
 
 基本上，开发人员传入一个错误的Handler函数，该函数将在进行API调用时发生错误。 
 
 对于API错误（或API返回的错误），我使用域ExampleAPPDomain创建NSError。 ApI错误具有不同的userInfo结构（例如，我向用户信息添加“类别”键）。 
 
 但有时错误是nsurlconnection错误...我也将该错误传递给错误处理程序。 
 
 所以我打电话给： 
 
errorHandler(error)
 
 有时传递给errorHandler函数的NSError错误是API错误，有时它是NSUrlConnection类型错误（如网络错误）。 
 
 我怎样才能更好地处理这些错误？ 例如，在错误处理程序代码中，开发人员必须检查域中的错误，以查看它的类型（NSURLDomain与ExampleAPPDomain）并相应地处理它。 这是两种错误之间不同的唯一方法。 
 
 处理APP错误与NSUrlConnection连接错误的标准方法是什么？ 

I am building an SDK. 
 
Basically developers pass in a error Handler function that will be called with the error that occurs when making an API call.
 
For API errors (or errors returned by the API), I create an NSError with domain ExampleAPPDomain. ApI Errors have a different userInfo structure (I add a "category" key to the user info, for example). 
 
But sometimes the error is a nsurlconnection error ... I also pass that error to the error handler.
 
so I call:
 
errorHandler(error)
 
sometimes the NSError error passed into errorHandler function is an API error and sometimes it is a NSUrlConnection type error (like a network error).
 
How can I best handle those errors differently? For example, in the error handler code, developers would have to check the domain for the Error to see what type it is (NSURLDomain vs ExampleAPPDomain) and handle it accordingly. That is the only way to differently between both errors.
 
What is the standard way of handling APP errors vs NSUrlConnection connected errors for something like this?

原文：https://stackoverflow.com/questions/19389869