4 ms·
My read is that without id's, having broken-out calories like the GGP's is a broken data model and/or API. The API should be returning a sum of the calories for
by rhizome 15y ago
My read is that without id's, having broken-out calories like the GGP's is a broken data model and/or API. The API should be returning a sum of the calories for a particular order, which supports GP's "RPC" argument. Either that, or returning ingredient ids with their calories counts.
- masklinn 15y ago> My read is that without id's, having broken-out calories like the GGP's is a broken data model and/or API. IDs are not involved at any point, and are not even relevant to bsaunder's comment. > Either that, or returning ingredient ids with their calories counts. An API which returns identifiers is not a REST API, so this statement makes no sense. Now more to the point, bsaunder is simply looking for a way to fetch a subset of a resource by providing some sort of filter. I truly do not see why that would not be restful, it's simply a search query, what do you think happens when you search something in Google? It returns a resource which is the subset of an other resource (their complete index, which they don't expose but that does not really matter), and as far as I can tell nobody's accused search engines of failing to be restful yet. (the sum stuff doesn't even make sense)