News for hackers. Stuff that matters.

A comment on Problems with RESTful APIs (2015). Parent comment

Re:Problems with RESTful APIs (2015) by int_19h on Wednesday March 01, 2017 @05:39AM (#13762763)
Because applications have state. In fact, the vast majority of reads in any applications are stateful (the database backing your app is also state, you know; I'm not talking just about session state here).

By "pure" here I mean that we're talking about a pure function of its inputs.

[ Parent | on HN ]
Re:Problems with RESTful APIs (2015) by icebraining on Wednesday March 01, 2017 @08:08AM (#13763366)
Why do you need to distinguish between those? In fact, if the function is pure, why not run it on the client?
[ Parent | on HN ]
Re:Problems with RESTful APIs (2015) by int_19h on Wednesday March 01, 2017 @01:51PM (#13766921)
Because the server has more computational resources, for example. It's a very rare scenario in general, but it does happen.

Why distinguish? Because if you know that the results are not affected by server state, they can be cached much more aggressively.

[ Parent | on HN ]