News for hackers. Stuff that matters.
Re:Idempotency Is Easy Until the Second Request Is Different by stickfigure on Tuesday May 12, 2026 @01:08AM (#48104411)
Nobody cares. These are short lived transactions (generally milliseconds); collisions are a rare edge case; it's fine to block. One request succeeds, the other gets a dup error (or a replay).

You could invent your own more sophisticated idempotency API but good luck finding someone that wants to implement it or use it. What real-world problem are you trying to solve?

Re:Idempotency Is Easy Until the Second Request Is Different by pdonis on Tuesday May 12, 2026 @11:25AM (#48109698)
> Nobody cares.

Meaning, clients don't care about the thing I asked about?

> What real-world problem are you trying to solve?

I'm trying to understand your answers to my questions. When there seems to me to be something missing, I ask about it.

Re:Idempotency Is Easy Until the Second Request Is Different by stickfigure on Tuesday May 12, 2026 @12:48PM (#48110833)
Correct, clients don't care to be notified if some other short lived request is in flight.