restful-architecture

问题 I'm having a real hard time conceptually understanding something proper concerning URLs for versioned resources. Let's say I have an application that tracks recipes in a way very similar to a version control system, like old school like RCS or something. Each version can be a working copy for some time then have a new version created from it. Each version has comments associated with it and doesn't share comments. I can go back historically at any time and look at the recipe as it evolved,

问题 I'm having a real hard time conceptually understanding something proper concerning URLs for versioned resources. Let's say I have an application that tracks recipes in a way very similar to a version control system, like old school like RCS or something. Each version can be a working copy for some time then have a new version created from it. Each version has comments associated with it and doesn't share comments. I can go back historically at any time and look at the recipe as it evolved,

问题 I'm having a real hard time conceptually understanding something proper concerning URLs for versioned resources. Let's say I have an application that tracks recipes in a way very similar to a version control system, like old school like RCS or something. Each version can be a working copy for some time then have a new version created from it. Each version has comments associated with it and doesn't share comments. I can go back historically at any time and look at the recipe as it evolved,

问题 I'm having a real hard time conceptually understanding something proper concerning URLs for versioned resources. Let's say I have an application that tracks recipes in a way very similar to a version control system, like old school like RCS or something. Each version can be a working copy for some time then have a new version created from it. Each version has comments associated with it and doesn't share comments. I can go back historically at any time and look at the recipe as it evolved,

问题 Given the requirement other departments have for our REST API they would like to use POST not just for CREATE but for UPDATE OR CREATE . I know in a RESTful API PUT could or should be used for that, but because clients have to update information that is used to build the URI, we cannot use that. It would change the URI and make PUT not idempotent anymore... (the old URI would not exist after the first PUT ). tl;dr we cannot use PUT In the HTTP/1.1 specs POST is defined as The POST method is

问题 Given the requirement other departments have for our REST API they would like to use POST not just for CREATE but for UPDATE OR CREATE . I know in a RESTful API PUT could or should be used for that, but because clients have to update information that is used to build the URI, we cannot use that. It would change the URI and make PUT not idempotent anymore... (the old URI would not exist after the first PUT ). tl;dr we cannot use PUT In the HTTP/1.1 specs POST is defined as The POST method is

来源： https://stackoverflow.com/questions/45954230/rest-api-should-single-api-have-multiple-responsibilities

来源： https://stackoverflow.com/questions/45954230/rest-api-should-single-api-have-multiple-responsibilities

来源： https://stackoverflow.com/questions/45954230/rest-api-should-single-api-have-multiple-responsibilities

问题 I have some resource- UserProfile public UserProfile { public string Email{get;set;} public string Password{get;set;} } I want to change Email and Password separatly (only one for user at same time). I have web api controller for example /api/user/123 that handle requests in RESTful style. Follow the RESTful style i should have one method PUT which update the resource, but i have two task that update the same resource api/user/123. I need to add some feature to PUT request body like {email: