New answers tagged

1

A drag/drop UI typically encourages users to play around with the interface. You may not want to have every UI operation send data back to the server every time they interact with the interface. Depending on the specific interface it may not be an issue, but it's something to think about. What happens to the UI if the server response time starts to grow? How ...


0

One popular current 'state of the art' is to use a RESTful API service on the backend, and the front-end is responsible for data display and sending requests/commands to the server. This is usually done through simple HTTP requests to URLs with special meaning, but many other variants work generally the same way (with some varying details - think SOAP, etc). ...


2

If you value consistency then the service that stores the data should be the definitive 'master' source of what the data looks like. This means that the front end must defer to whatever the service says. Now that doesn't mean it cannot cache results, but it should not make assumptions about logic that may (or may not) be processed on the service. eg. Lets ...


0

I think that, exactly like you've pointed out, the big considerations would be What would happen if the implementation on the client or server side changes. How would future developers extend the API if it was written that way How would this design impact modularity/reuseability of the API What you're proposing would tightly couple part of the API to ...


4

I'm no expert on JS or PHP so there might be some caveats I'm not aware of, but these are some ideas that come to my mind when I see this. First off, I think your first idea is great. To answer the points you are raising: Is it okay to use the property "name" twice, since they are on different levels? I've read that it's better to keep the property ...



Top 50 recent answers are included