3 ms·
I think that's too strong: the response may have a component that is is non-deterministic. The important thing is that no matter how many times you call it the
by jefftk 5y ago
I think that's too strong: the response may have a component that is is non-deterministic. The important thing is that no matter how many times you call it the server state is the same.
- bastawhiz 5y agoAgreed. The state since the original success may have been mutated by another request since (or simply changed state as a result of any other async process), and the response may simply be a rendering of the latest server state. The response of the server absolutely should not be specified as being identical, since that's not how idempotent requests work. At that point, you're really just specifying a caching key for verbs that have side effects.
- sam0x17 5y agoYeah, it's more about there being no side effects after the first time than asserting anything about the actual response
- zepto 5y agoIf you distinguish the ‘response’ from the result, then I agree. Typically I think of the result as denoting the effect, and not the response message.