Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Could you please clarify what you mean by "you must not consider others as human beings but only as machines"? In addition, if I understand correctly, are you suggesting that it is better to build the application in the context of having two distinct kinds of resources (i.e. a service contact and an employee contact) and then make CRUD to each of them separately? Commented Apr 14, 2016 at 9:58
  • 1
    This is a great answer about concepts of REST. I am just saying that REST (AFAIK) should connect browser with server and rarely user with server. And yes, you understand correctly. I suggest to use two distinct kinds of resources. Commented Apr 14, 2016 at 10:05
  • 1
    @nik_m On the contrary - having the action embedded in the URL is not RESTful at all. The URLs in REST should identify resources, not actions. The actions are denoted by method verbs: e.g. GET /offices/1 gets the office resource representation, POST /offices creates a new office resource in the offices collection. Commented Apr 14, 2016 at 11:56