Timeline for Deciding on method idempotency approach
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 7, 2016 at 7:27 | comment | added | dstr | We're not going to replace/override the existing object but keep the existing one. This is a business decision. Neither we're returning the created object as a return value, just a 201 Created. | |
| Apr 6, 2016 at 21:18 | comment | added | JimmyJames | This is an interesting use case. In order for the call to be idempotent, the call needs to be side effect free. What this (very familiar) use case shows is that there's an expectation that creating a user is not side effect free and should not/ can not be implemented as an idempotent call. | |
| Apr 6, 2016 at 21:01 | history | answered | gbjbaanb | CC BY-SA 3.0 |