Dealing with API and error messages
We are in the process of constructing an API (using WCF).
Choosing a proper wording for referring compiler errors
Consider someone is writing a message (or a question at StackOverflow). The context is following:
What is the nicest (user-friendliest) way to tell a user about “Access Denied” error?
Our software implements a layer of role-based security to secure data access, in the form of access control lists. Whenever a user tries to do something that isn’t allowed, the software layer will receive an “access denied” error code or exception.
Am I handling my exceptions in a sensible manner?
I’m still restructuring the code I have been given to update on my current work project, and I’ve come to the point where I’m looking at how the code handles an ‘exceptional’ input, that doesn’t conform to the business logic.
How do I output an error when I’m determining how to output an error?
I’ve written an API which can be configured to signal errors in different ways (return values, debugging messages, or exceptions). I’ve got a check in place when the API is first initialized to see what type of error handling the client is requesting – what should I do when they request an undefined error handling type?
How do I output an error when I’m determining how to output an error?
I’ve written an API which can be configured to signal errors in different ways (return values, debugging messages, or exceptions). I’ve got a check in place when the API is first initialized to see what type of error handling the client is requesting – what should I do when they request an undefined error handling type?
How do I output an error when I’m determining how to output an error?
I’ve written an API which can be configured to signal errors in different ways (return values, debugging messages, or exceptions). I’ve got a check in place when the API is first initialized to see what type of error handling the client is requesting – what should I do when they request an undefined error handling type?
How do I output an error when I’m determining how to output an error?
I’ve written an API which can be configured to signal errors in different ways (return values, debugging messages, or exceptions). I’ve got a check in place when the API is first initialized to see what type of error handling the client is requesting – what should I do when they request an undefined error handling type?
How do I output an error when I’m determining how to output an error?
I’ve written an API which can be configured to signal errors in different ways (return values, debugging messages, or exceptions). I’ve got a check in place when the API is first initialized to see what type of error handling the client is requesting – what should I do when they request an undefined error handling type?
How do I output an error when I’m determining how to output an error?
I’ve written an API which can be configured to signal errors in different ways (return values, debugging messages, or exceptions). I’ve got a check in place when the API is first initialized to see what type of error handling the client is requesting – what should I do when they request an undefined error handling type?