Hi,
What's very important is that we don't try to redefine HTTP error codes.
If there's an error code for it, then it should be used and it should be
enough in most cases for the client to understand what happened.
I've seen some horrible APIs, which return generic error code and one
should read the returned error message to understand what's wrong.
That's not how a REST-interface should work.
- Micke
On 13.02.2015 16:08, Viliam Rockai wrote:
Hey all,
Another REST issue we should agree on: The standard for error responses.
I've found, that there are several standards we can follow (or create
our own):
http://stackoverflow.com/a/14538774/3252949
In my opinion it's fine to stick with the JSON API:
http://jsonapi.org/format/#errors
or stick with even simpler google style guide:
https://google-styleguide.googlecode.com/svn/trunk/jsoncstyleguide.xml?sh...
WDYT?
Viliam
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev