In my view, the resource should pass me an object that I can immediately display in the view. I understand that this has its limitations because I'm not the only one using the resource. However, I think in an ideal scenario, the server should relieve the client of as much work as possible since we know and control what machine the server will be. The client on the other side is someone else's computer and we don't know how much that machine can stem. So, I'm wondering what the best strategy in cases like that is. I'm pretty much unexperienced in this area and I would like to get some outside input that might give me a different perspective.
- How are you negotiating API designs?
- Is there a tendency as to how your APIs are designed i.e. how much mapping do you do in the front-end/back-end?
- Also, if the server doesn't pass me the data in a useful manner, what's the need for a server after all? (I'm intentionally exaggerating.)
- Are there any patterns that help me dealing with data transformations like that?