3 ms·
What do you propose as alternative to these issues?
by ericingram 14y ago
What do you propose as alternative to these issues?
- 3amOpsGuy 14y agoGet rid of the .json, use a specific media type, if at all possible refer to a schema description in the metadata presented. Search is a service, not a part of a resource. Whether a seperate search service aggregating all different REST resources is supplied or not is irrelevant in the example case as resource collections can be filtered, which the article highlights (the colour= parameter), for a dogs resource, or a phonebook resource etc. filtering on attributes (which can use wildcards or regexes as seen fit to do so) provides the necessary functionality anyway. Search is a diversion in these cases. Go versionless.
- ericingram 14y agoI agree with going versionless (though I can see the case for it also depending on how the API is intended to be used). Get rid of .json? Make it optional sure, but allow it if the client wants to be specific. Seems like a good feature in that sense (optional with a good default). I agree that search should not be a resource, but perhaps a parameter for filtering in addition to explicitly named param filters. Thanks for sharing your thoughts on it.