API responses should be signed

Re:API responses should be signed by jayd16 on Monday January 20, 2020 @02:20AM (#22097004)

This might not be the most salient place to start when critiquing this article but it did irk me that they get the definition of idempotent wrong even while linking to Wikipedia.

>That is, the data returned from a query is always the same.

That is not correct. Only the system state remains the same. As stated in the linked wiki page:

>[...] the end result is always the same as the result of the initial execution, even if the response differs.

[ Parent | on HN ]

Re:API responses should be signed by edent on Monday January 20, 2020 @02:34AM (#22097084)

That's a fair criticism. What is the correct word for "this request always generates an identical response"?

[ Parent | on HN ]

Re:API responses should be signed by matharmin on Monday January 20, 2020 @02:36AM (#22097094)

Immutable

[ Parent | on HN ]

Re:API responses should be signed by DarkWiiPlayer on Monday January 20, 2020 @08:05AM (#22098500)

Immuteble describes data, whereas an API call is more like a function call, in which case we'd call the property "referential transparency", which means, a function always returns the same result for a given input value.

"referential transparency" makes up half the definition of a "pure" function, with the other half being the absence of side effects.

[ Parent | on HN ]

Re:API responses should be signed by edent on Monday January 20, 2020 @02:42AM (#22097117)

Aha! Yes. Thanks. I'll update the blog post.

[ Parent | on HN ]

Re:API responses should be signed by opifex on Monday January 20, 2020 @06:46PM (#22103039)

Deterministic

[ Parent | on HN ]

Re:API responses should be signed by marton78 on Monday January 20, 2020 @03:33AM (#22097339)

Pure

[ Parent | on HN ]

Re:API responses should be signed by DarkWiiPlayer on Monday January 20, 2020 @08:07AM (#22098513)

Pure also means no side effects, which isn't, strictly speaking, what OP means :)

[ Parent | on HN ]