Hot answers tagged

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 ...


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 ...


1

First you need to decide how to make this change. Either update all the necessary invoice date fields or cancel the invoice and copy/rebuild all the data with a different date and possibly invoice number. Once you can code making this change, you can then decide on how to apply it to many invoices. If you think the problem is going to continue to stem from ...


1

In my programming environment (MacOS X / iOS) it is quite trivial - I create a semaphore, start the asynchronous request, the asynchronous request will unlock the semaphore when it's done, and then I lock the semaphore (which will wake up when the asynchronous request is done). Maybe six or eight lines of code. On the other hand, synchronous requests, ...


1

So what is really a resource, why it should be a mapping to one or more entities and what are some examples? When in doubt about anything relating to REST, consider the question in the context of the web. Here's a flow: I want to read Bob's homepage I know (probably because some other web page told me) that there is a http request handler with the id ...



Only top voted, non community-wiki answers of a minimum length are eligible