A fair point. I was referring to the api being separate from the frontend, not what the api is returning. But I could see someone designing their application the way you describe.
And when someone does design their application in that manner, the various benefits of doing things 'right' start to pay off.
If a resource or result is addressable it means that a 3rd party can build an API that integrates with my API and link straight to results of certain queries.
Granted that this would be hard in the context of the dropbox API, because they already 'break' a lot other rules.
Yes, if reusable/sharable queries are something you want, then you don't really have a choice but to expose an API for creating and retrieving them. Not sure if you're trying to make some other point related to the `Accept:` header the parent comment was about.
treve|11 years ago
If a resource or result is addressable it means that a 3rd party can build an API that integrates with my API and link straight to results of certain queries.
Granted that this would be hard in the context of the dropbox API, because they already 'break' a lot other rules.
davidism|11 years ago