3 ms·
Nitpick, but the "GET /people/{id}/exists" in the example to check if the instance exists is a bit weird, would suggest "HEAD /people/{id}" for this type of ope
by Rezo 12y ago
Nitpick, but the "GET /people/{id}/exists" in the example to check if the instance exists is a bit weird, would suggest "HEAD /people/{id}" for this type of operation.
- Goopplesoft 12y agoActually the resource should typically 404 to indicate it doesn't exists (generally speaking for http apis).
- euank 12y agoYeah, the HEAD or GET should return a 404 on not existence; however, the HEAD also won't return data which is the point. GET implies that you have need of the returned data (presumably all the properties of that person). GET is for "it exists AND I want to know about it". HEAD really is more appropriate here.
- enjoyjava 12y agoHEAD is a good fit. We'll add support for that. Please open github issues to help us track the feature requests or bug fixes at https://github.com/strongloop/loopback/issues https://github.com/strongloop/loopback/issues.
- s_kilk 12y agoYeah, this is a bit weird. For some reason I'm still surprised when I see pseudo-REST being passed off as RESTful.
- nailer 12y agoThey have a resource called 'push' too. I don't know what a 'push' is.