public User{
int id;//key
int code;//員工編號 唯一
String name;
...
}
GET /employee/{id} 根據(jù)ID獲取人員
GET /employee/{code}
如上:code也是唯一的,如果這么命名是會混淆,應(yīng)該如何命名?
走同樣的路,發(fā)現(xiàn)不同的人生
Getting the only user is /employee/{id}. What should be obtained through this URL is the user entity object.
For the properties inside the entity object: code . Should not be obtained by exposing the URL.
The first step when designing RESTURL is resource abstraction. It is necessary to clearly distinguish which resources can be extracted and design a unique URL. What can’t be done
RESTful resources generally use plural numbers. I think code can also be used as a search condition: /employees/search?code=xxx. Of course, code can also be obtained and changed as a resource of employee, but when searching for employee through code, it should be Belongs to the search function.