When you make a web service call, you want to report the problem to the user save as you do for any other part of the program, and that is through an exception object. This post talks about converting the JSON received back into an exception object so that it can be reported properly. This is the fourth post in a series about translatable errors for REST web services. Continue reading
Second in a series on translatable exceptions, this discusses how an error message should be returned as JSON from a web-service API so that it the calling program can display the error in the right language for the user. Continue reading
If you are going to exchange data structures between programs you have many choices. Of these, JSON is the best choice in general, and specifically a better choice than XML, and this post explains why. Continue reading
This is a suggestion for how to design the JSON/REST protocol between the Angular application and the server, to handle creation of items easily and conveniently. Use a special ID value to indicate that the object does not exist on the server, and update like normal. The server detects this and creates it on demand. Continue reading
In this post, I lay out the reason that you should always transfer dates in a JSON/REST API as an integer epoch value: the number of milliseconds since Jan 1, 1970. If you think it should be anything else, please read on….