Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 1
    @JacquesB: The argumentation for any client-side cache remains the same regardless of what specific data (or data format) is being cached. Commented May 31, 2023 at 6:12
  • 2
    @JacquesB The argumentation for any client-side cache remains the same regardless of what specific data (or data format) is being cached. The argumentations for client-side caches and serverside caches are different, but individually they are consistent for any kind of data that you are working with, regardless of it being JSON data, images, web pages, ... Commented May 31, 2023 at 6:16
  • 1
    @JacquesB: I can make the same argument about browsers being able to store the result they get from a URL and not fetch it a second time. The reason for wanting to cache something is irrespective of the specific data format that is being cached. Commented May 31, 2023 at 10:48
  • 1
    @JacquesB "which means the code already have the data!" Not necessarily. Data, especially from APIs can change. And you do things like put in a If-Modified-Since header to only pull data when it is actually changed on the server. I've never understood why you wouldn't follow HTTP standards when you can. Did the SOAP-WSDL debacle teach us nothing? Commented May 31, 2023 at 13:23
  • 1
    @JacquesB HTTP level caching is not necessarily happening client-side, but may occur in the intermediaries in the network infrastructure, making responses faster and taking the load off of the server. Commented May 31, 2023 at 20:20