4 ms·
Idempotent means that the side effects of n > 0 requests are the same as for a single request. The "update status" method is not idempotent, as calling it multi
by dandelany 16y ago
Idempotent means that the side effects of n > 0 requests are the same as for a single request. The "update status" method is not idempotent, as calling it multiple times would post multiple statuses. I think the parent's statement is sound.
A request that is side effect free is idempotent by definition.
- makmanalp 16y agoRight, but the concept was created to talk about distributed systems and remote procedure calls where if a failure happened on your end and you didn't know if the procedure call worked, you wouldn't have to check if it worked before retrying. So it doesn't quite fit here. Also, I don't think idempotence is a solution to this since a) This is more of a security issue, and less of a systems design one and b) you might actually have a legitimate use case for multiple posts
- pohl 16y ago...the concept was created to talk about distributed systems and remote procedure calls... I'm pretty sure the concept's use in mathematics predates that by far.
- riffraff 16y agoso, if the first call posts a tweet and the second does not, we shall be satisfied? I stand by the side effect free side :) (notice that tweet posting is actually kind of idempotent in twitter: if you post the same message twice, it will only appear once)
- deleted 16y ago[deleted]