Idempotency: Difference between revisions
Jump to navigation
Jump to search
m (Thexa4 moved page Idempotent to Idempotency) |
No edit summary |
||
| Line 5: | Line 5: | ||
* DELETE requests are idempotent because DELETEing a resource that's no longer there will result in the same deleted resource. | * DELETE requests are idempotent because DELETEing a resource that's no longer there will result in the same deleted resource. | ||
* PUT requests are also idempotent because if you set the state for an object to the same value twice it will still have the value you provided. | * PUT requests are also idempotent because if you set the state for an object to the same value twice it will still have the value you provided. | ||
[[Category: Terminology]] | |||
Latest revision as of 09:21, 3 December 2020
Idempotency means that you can perform an action more than once without changing any state.
Examples
- GET requests can be done more than once because they are supposed to not change any state at all
- DELETE requests are idempotent because DELETEing a resource that's no longer there will result in the same deleted resource.
- PUT requests are also idempotent because if you set the state for an object to the same value twice it will still have the value you provided.