idempotent

Let's say I want to build a REST service for making notes that looks something like this: GET /notes/ // gives me all notes GET /notes/{id} // gives the note identified by {id} DELETE /notes/{id} // delete note PUT /notes/{id} // creates a new note if there is no note identified by {id} // otherwise the existing note is updated Since I want my service to be indempotent I'm using PUT to create and update my notes, which implies that the ids of new notes are set/generated by the Client. I thought of using GUIDs/UUIDs but they are pretty long and would make remembering the URLs rather dificult.

I'm designing a RESTful web service utilizing ROA(Resource oriented architecture). I'm trying to work out an efficient way to guarantee idempotence for PUT requests that create new resources in cases that the server designates the resource key. From my understanding, the traditional approach is to create a type of transaction resource such as /CREATE_PERSON. The the client-server interaction for creating a new person resource would be in two parts: Step 1: Get unique transaction id for creating the new PERSON resource::: **Client request:** POST /CREATE_PERSON **Server response:** 200 OK

I am using Ansible and I want to run a task only once. I follow the documentation about how to configure and run a task only once - name: apt update shell: apt-get update run_once: true But when I run Ansible, it always runs this task. How can I run my task only once. The run_once option will run every time your Playbook/tasks runs, but will only run it once during the specific run itself. So every time you run the play, it will run, but only on the first host in the list. If you're looking for a way to only run that command once, period, you'll need to use the creates argument. Using your

From a lot of articles and commercial API I saw, most people make their APIs idempotent by asking the client to provide a requestId or idempotent-key (e.g. https://www.masteringmodernpayments.com/blog/idempotent-stripe-requests ) and basically store the requestId <-> response map in the storage. So if there's a request coming in which already is in this map, the application would just return the stored response. This is all good to me but my problem is how do I handle the case where the second call coming in while the first call is still in progress? So here is my questions I guess the ideal

I have spent a lot of time recently reading the HTTP 1.1 specification and relating it to REST. I have found that there are two interpretations of the HTTP DELETE method in regards to its "idempotency" and safety. Here are the two camps: If you delete a resource with HTTP DELETE, and it succeeds (200 OK), and then you try to delete that resource N number of times, you should get back a success message (200 OK) for each and every one of those delete calls. This is its "idempotencyness". If you delete a resource with HTTP DELETE, and it succeeds (200 OK), and then you try to delete that resource