Request response method and device

Abstract

The invention provides a request response method and device, and the method comprises the steps: firstly responding to a network request of a browser, and searching a caching strategy corresponding to the network request; the caching strategy comprises caching time efficiency of caching response data corresponding to the network request; then, on the basis of the cache time efficiency, the cache timestamp of the cache response data and the current timestamp, whether the cache response data is valid or not is determined; and finally, under the condition that the cache response data is valid, feeding back the cache response data to the browser. According to the method and the device, different caching strategies can be configured according to the characteristics of different network requests, so that the caching response data of different network requests have different caching timeliness, the reliability of the caching response data is improved, new data does not need to be acquired from the server in each request, and the data communication frequency is reduced.

Description

technical field [0001] The present disclosure relates to the field of computer technology, and in particular, to a request-response method and device. Background technique [0002] In order to improve the access speed of the web page and reduce the pressure on the server, the browser usually adopts a caching scheme. Common caching schemes include the Hyper Text Transfer Protocol (Hyper Text Transfer Protocol, HTTP) standard caching scheme and the in-page caching scheme. HTTP standard caching schemes mainly include strong caching and negotiated caching. Strong caching will set the cache time limit for cached data, while negotiated caching will negotiate with the client and the server, and the server will determine whether the cache is available according to the time limit and the resource itself. The above two solutions It is difficult to implement in the case of frequent updates of uncertainty and no entity file for requesting data. The in-web page caching solution includes...

AI Technical Summary

Problems solved by technology

HTTP standard caching solutions mainly include strong caching and negotiation caching. Strong caching will set the caching time limit for the cached data. Negotiating caching is negotiated between the client and the server. The server judges whether the cache is available based on the time limit and the resource itself. The above two solutions Difficult to implement when uncertain updates are frequent and there is no entity file requesting data

The in-webpage caching scheme includes snapshot cache and timing cache, which can be applied to the situation where the requested data does not exist in physical files, but snapshot cache still needs to request new data every time, and timing cache is also difficult to judge the update time of data, which makes it easy to get to expired data

Images