Home > Net > API/address remains the same, according to the parameters for the specific implementation, how to do
API/address remains the same, according to the parameters for the specific implementation, how to do
Time:10-04
Such as api.taobao.com so a fixed url
CMD=the order according to the transmission, such as parameters. The create is invoked to create the order. The update is modified, the order. The delete will delete
Generally they are based on DNS or what to do, code usually need how to do?
CodePudding user response:
Address remains the same, HTTPMETHOD can
Increase with the HttpPost Modified with HttpPut Modify the local use HttpPatch Remove with HttpDelete
Can,
CodePudding user response:
If it is the ordinary The API/user/create Then basic is routing.
If this is the API? CMD=order. The create There is a strong possibility is reflected. The class through the API to find the order under the create method... Then go to receive post parameters...
CodePudding user response:
For webapi, this is just an interface, parameter is CMD and other additional In this interface you again to determine what is CMD After you with his own factory pattern If even the switch will be fine
CodePudding user response:
Routing
No matter he used that skill, generally referred to as the routing, you can use nginx routing, you can use the mq routing, you can use the MVC routing, you can use the eventbus routing
CodePudding user response:
Here is the.net version, other routing the ans not
At the very least, the MVC routing, and had never rules must be written as {control}/{action}