Let's say you have a blog with caching enabled. The first time someone visits your homepage they receive the page in the normal way: The request is received, processed on the server, and the resulting web page to be displayed is transformed into an HTML file and sent to the visitor's web browser. Since caching is enabled, the server stores this HTML file – usually in its 'random access memory' (or RAM), which is extremely fast.
The next time you, or anyone else, views the homepage, the jiangxi mobile number database server doesn't need to do the processing and conversion to HTML. Instead, it simply sends the already prepared HTML file to the browser. Different types of caches As you may have understood, caching is a technique that stores a copy of a given resource and serves it again when requested. When a web cache has a requested resource in its warehouse, it intercepts the request and returns its copy instead of re-downloading from the origin server.
This achieves several objectives: it relieves the load on the server which does not need to serve all clients, and it improves performance by being closer to those who request it. For a website, it is an important component to achieve high performance. On the other hand, it must be configured correctly because not all resources remain identical forever: it is therefore important to cache a resource only until it changes, no longer.
- Board index
- All times are UTC
- Delete cookies
- Contact us