CN116820639A - Method for page caching, storage medium and processor - Google Patents

Abstract

The embodiment of the application provides a method for page caching, a storage medium and a processor. The method comprises the following steps: acquiring a page access identifier of a page, wherein the page access identifier is sent after a client detects that a user accesses the page; acquiring sub-application configuration data sent by a configuration module, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier; under the condition that a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data, acquiring a first history route identifier of the loaded sub-application in a sub-application cache module; under the condition that a target sub-application identifier exists in the first historical route identifier, loading a sub-application corresponding to the page access identifier through a sub-application loading module; determining a target page route identifier matched with the target sub-application identifier from the page route identifiers; and sending the target page route identification to the sub-application so that the sub-application caches the page according to the target page identification, thereby reducing the time for loading the same sub-application.

Description

Method for page caching, storage medium and processor

Technical Field

The present application relates to the field of computers, and in particular, to a method, a storage medium, and a processor for page caching.

Background

Currently, micro front ends load sub-applications through route matching. After the sub-application is loaded, the sub-application completes state isolation and realizes independent operation, and the main application does not control the sub-application state any more. At this time, if the user switches back and forth among the plurality of sub-applications, the main application may independently load a new sub-application. Because of the state isolation between the main application and the sub-application, after the new sub-application is loaded, the page cache of the previous sub-application is invalid, the main application is required to load the sub-application again, the loading time is long, and the speed of accessing the page by the user is easily influenced.

Disclosure of Invention

The embodiment of the application aims to provide a method, a storage medium and a processor for page caching.

In order to achieve the above object, a first aspect of the present application provides a method for page caching, applied to a main application, where a cache control device includes a configuration module, a cache module, and a loading module, where the cache module includes a sub-application cache module, and the loading module includes a sub-application loading module, including:

acquiring a page access identifier of a page, wherein the page access identifier is sent after a client detects that a user accesses the page;

Acquiring sub-application configuration data sent by a configuration module, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier;

under the condition that a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data, acquiring a first history route identifier of the loaded sub-application in a sub-application cache module;

under the condition that a target sub-application identifier exists in the first historical route identifier, loading a sub-application corresponding to the page access identifier through a sub-application loading module;

determining a target page route identifier matched with the target sub-application identifier from the page route identifiers;

and sending the target page route identification to the sub-application so that the sub-application caches the page according to the target page identification.

In the embodiment of the application, the method further comprises the following steps: before acquiring a page access identifier of a page, acquiring sub-application initial data sent by a client, wherein the sub-application initial data refers to initial data of a sub-application required to be mounted by a main application; screening the sub-application initial data according to a preset rule, and taking the screened sub-application initial data as sub-application configuration data; the sub-application configuration data is sent to the configuration module to store the sub-application configuration data by the configuration module.

In the embodiment of the application, the method further comprises the following steps: under the condition that the first historical route identifier does not have the sub-application identifier corresponding to the target sub-application identifier, the sub-application corresponding to the page access identifier is loaded for the first time; acquiring first resource data of a sub-application corresponding to the page access identifier, wherein the first resource data is sent by a client after receiving a first acquisition request of the first resource data; and sending the first resource data to the sub-application caching module so that the sub-application caching module caches the first resource data and updates the first historical route identification.

In an embodiment of the present application, the cache control device further includes a message module, and sends the destination page route identifier to the sub-application, so that the sub-application caches the page according to the destination page identifier, including: and sending the target page route identification to the message module, so that the target page route identification is sent to the sub-application through the message module, and the sub-application caches the page according to the target page identification.

In the embodiment of the application, the method further comprises the following steps: detecting whether the page access identifier is updated; and returning to the step of acquiring the page access identification of the page under the condition of determining the page access identification update so as to load the corresponding sub-application according to the re-acquired page access identification.

A second aspect of the application provides a processor configured to perform the above-described method for page caching.

A third aspect of the application provides a machine-readable storage medium having stored thereon instructions which, when executed by a processor, cause the processor to be configured to perform the method for page caching described above.

The fourth aspect of the present application provides a method for page caching, where the cache control device includes a configuration module, a cache module and a loading module, the cache module includes a sub-application cache module, the loading module includes a sub-application loading module, and the method includes:

after detecting that a user accesses a page, the client sends a page access identifier of the page to a main application;

the configuration module sends sub-application configuration data to the main application, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier;

under the condition that the main application determines that a target sub-application identifier corresponding to the page access identifier exists in sub-application configuration data, the sub-application cache module sends a first history route identifier of the loaded sub-application to the main application;

under the condition that the main application determines that the first historical route identifier has the identifier corresponding to the target sub-application, the sub-application loading module loads the sub-application corresponding to the page access identifier;

The main application determines a target page route identifier matched with a target sub-application identifier from the page route identifiers, and sends the target page route identifier to the sub-application;

the sub-application caches the page according to the destination page route identification.

In the embodiment of the application, the cache module comprises a page cache module, the loading module comprises a page loading module, and the sub-application caches the page according to the target page identification, wherein the sub-application comprises: the sub-application judges whether the page access identifier needs to be cached according to the target page route identifier; under the condition that the page access identification needs to be cached according to the target page route identification, the page cache module sends a second history route identification of the loaded page to the sub-application; the sub-application judges whether a page access identifier exists in the second historical route identifier; and under the condition that the sub-application determines that the page access identifier exists in the second historical route identifier, loading resource data corresponding to the page route identifier in the page buffer module through the page loading module so as to load the page.

In the embodiment of the application, the method further comprises the following steps: under the condition that the sub-application determines that the page access identifier does not exist in the second historical route identifier, the sub-application loads the page for the first time; the client sends the second resource data of the page to the sub-application after receiving a second acquisition request of the second resource data; and the sub-application sends the second resource data to the page buffer module so that the page buffer module buffers the second resource data and updates the second historical route identification.

In the embodiment of the application, the method further comprises the following steps: before acquiring a page access identifier of a page, sub-application initial data sent by a client side is sent to a main application, wherein the sub-application initial data refers to initial data of a sub-application required to be mounted by the main application; the main application screens the initial data of the sub-application according to a preset rule, so that the screened initial data of the sub-application is used as the configuration data of the sub-application; the main application sends the sub-application configuration data to the configuration module to store the sub-application configuration data through the configuration module.

In the embodiment of the application, the method further comprises the following steps: the sub-application detects whether the route identification of the target page is updated or not; and returning to the step of judging whether the page access identifier needs to be cached according to the target page route identifier under the condition that the sub-application determines that the target page route identifier is updated, so that the sub-application rebuffers the corresponding page.

In the embodiment of the present application, the cache control device further includes a message module, and sending the destination page route identifier to the sub-application includes: and sending the target page route identification to the message module so as to send the target page route identification to the sub-application through the message module.

A fifth aspect of the application provides a processor configured to perform the method for page caching described above.

A sixth aspect of the application provides a machine-readable storage medium having stored thereon instructions which, when executed by a processor, cause the processor to be configured to perform the method for page caching described above.

According to the technical scheme, under the condition that state isolation exists between the main application and the sub-application, the main application can determine the loading mode of the sub-application according to the sub-application configuration data and the first history route identification of the loaded sub-application, the main application is prevented from repeatedly loading the same sub-application, the time for loading the same sub-application is greatly reduced, and the speed of a user for accessing a page is greatly improved.

Additional features and advantages of embodiments of the application will be set forth in the detailed description which follows.

Drawings

The accompanying drawings are included to provide a further understanding of embodiments of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain, without limitation, the embodiments of the application. In the drawings:

FIG. 1 schematically illustrates a flow diagram of a method for page caching according to an embodiment of the application;

FIG. 2 schematically illustrates a flow diagram of a method for page caching according to another embodiment of the application;

FIG. 3 schematically shows a flow diagram of a method for page caching according to a further embodiment of the application;

FIG. 4 schematically illustrates a block diagram of a micro front-end cache control device according to an embodiment of the present application;

FIG. 5 schematically illustrates a timing diagram of sub-application loading according to an embodiment of the application;

FIG. 6 schematically illustrates a timing diagram of a page cache according to an embodiment of the application;

fig. 7 schematically shows an internal structural view of a computer device according to an embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it should be understood that the detailed description described herein is merely for illustrating and explaining the embodiments of the present application, and is not intended to limit the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

Fig. 1 schematically shows a flow diagram of a method for page caching according to an embodiment of the application. As shown in fig. 1, in an embodiment of the present application, a method for page caching is provided and applied to a main application, where a cache control device includes a configuration module, a cache module, and a loading module, where the cache module includes a sub-application cache module, and the loading module includes a sub-application loading module, and includes the following steps:

Step 101, acquiring a page access identifier of a page, wherein the page access identifier is sent after a client detects that a user accesses the page.

Step 102, obtaining sub-application configuration data sent by a configuration module, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier.

Step 103, under the condition that a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data, acquiring a first history route identifier of the loaded sub-application in the sub-application cache module.

Step 104, loading the sub-application corresponding to the page access identifier through the sub-application loading module under the condition that the target sub-application identifier exists in the first historical route identifier.

Step 105, determining a target page route identification matched with the target sub-application identification from the page route identifications.

And step 106, the target page route identification is sent to the sub-application, so that the sub-application caches the page according to the target page identification.

After the client detects that the user accesses the page, the client may send a signal to the processor that the user accessed the page. The processor may send a signal to the client to obtain a page access identification of the page based on the signal. The client may send the page access identifier of the page to the processor after receiving the signal to obtain the page access identifier of the page. The processor may obtain a page access identification of the page. The processor may then send a request to the configuration module to obtain the sub-application configuration data. The configuration module may send the sub-application configuration data to the processor after receiving the request. The processor may obtain the sub-application configuration data sent by the configuration module. The sub-application configuration data comprises a sub-application identifier and a page route identifier. Further, the sub-application configuration data may also include a deployment path for the sub-application.

The processor may determine whether a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data. If the target sub-application identifier corresponding to the page access identifier does not exist in the sub-application configuration data, the sub-application configuration data can determine that the sub-application identifier is not matched with the page access identifier, and the sub-application configuration data is possibly the main application identifier. If the target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data, the processor may send a request for acquiring the first history route identifier of the loaded sub-application to the cache control device. The sub-application cache module in the cache control device may send the first history route identification of the loaded sub-application to the processor. The processor may determine whether a target sub-application identifier exists therein according to the obtained first historical route identifier. Under the condition that the target sub-application identifier exists in the first historical route identifier, the sub-application corresponding to the page access identifier can be loaded through the sub-application loading module. That is, the resource data of the sub-application corresponding to the page access identifier is cached in the sub-application cache module at this time, and the sub-application corresponding to the page access identifier can be loaded by the sub-application loading module. The processor may then determine a target page route identifier from the page route identifiers that matches the target sub-application identifier, and send the target page route identifier to the sub-application to cause the sub-application to cache the page according to the target page identifier.

According to the technical scheme, under the condition that state isolation exists between the main application and the sub-application, the main application can flexibly determine the loading mode of the sub-application according to the sub-application configuration data and the first history route identification of the loaded sub-application, the main application is prevented from repeatedly loading the same sub-application, the time for loading the same sub-application is greatly reduced, and the speed of a user for accessing a page is greatly improved.

In one embodiment, the method further comprises: before acquiring a page access identifier of a page, acquiring sub-application initial data sent by a client, wherein the sub-application initial data refers to initial data of a sub-application required to be mounted by a main application; screening the sub-application initial data according to a preset rule, and taking the screened sub-application initial data as sub-application configuration data; the sub-application configuration data is sent to the configuration module to store the sub-application configuration data by the configuration module.

The processor may obtain the sub-application initial data sent by the client before obtaining the page access identification of the page. The sub-application initial data is initial data of the sub-application which is required to be mounted by the main application. And then, the processor can screen the initial data of the sub-application according to a preset rule so as to take the screened initial data of the sub-application as the configuration data of the sub-application. The processor may then send the sub-application configuration data to the configuration module to store the sub-application configuration data by the configuration module. The configuration module stores the configuration data of the sub-application, and when the main application is in state isolation with the sub-application, the loading mode of the sub-application can be controlled according to the configuration data of the sub-application.

In one embodiment, the method further comprises: under the condition that the first historical route identifier does not have the sub-application identifier corresponding to the target sub-application identifier, the sub-application corresponding to the page access identifier is loaded for the first time; acquiring first resource data of a sub-application corresponding to the page access identifier, wherein the first resource data is sent by a client after receiving a first acquisition request of the first resource data; and sending the first resource data to the sub-application caching module so that the sub-application caching module caches the first resource data and updates the first historical route identification.

In the case that the first historical route identifier does not exist in the first historical route identifier, the processor can load the sub-application corresponding to the page access identifier for the first time. Thereafter, the processor may send a first acquisition request to the client to acquire first resource data of the sub-application corresponding to the page access identification. The client may send the first resource data of the corresponding sub-application to the processor after receiving the first acquisition request. The processor may obtain first resource data of the sub-application corresponding to the page access identification. The processor may then send the first resource data to the sub-application cache module to cause the sub-application cache module to cache the first resource data and update the first historical route identification. That is, when the sub-application is loaded for the first time, the resource data of the sub-application loaded for the first time may be stored to the sub-application cache module of the cache control device. Therefore, after the main application is isolated from the sub-application state, the same sub-application can be loaded through the resource data of the loaded sub-application in the sub-application cache module, so that the repeated loading of the same sub-application after the sub-application is switched is avoided, and the loading efficiency and speed are improved.

In one embodiment, the cache control device further includes a message module that sends the destination page route identifier to the sub-application, so that the sub-application caches the page according to the destination page identifier, including: and sending the target page route identification to the message module, so that the target page route identification is sent to the sub-application through the message module, and the sub-application caches the page according to the target page identification.

The cache control device also comprises a message module. The message module is used for communicating real-time messages between the main application and the sub-application. The processor may send the target page route identification to the message module after determining a target page route identification matching the target sub-application identification from the page route identifications. The message module may send the received destination page route identifier to the sub-application, so that the sub-application caches the page according to the destination page identifier. A message communication channel is established between the message module and the sub-application, the page access identification can be obtained under the condition of being isolated from the state of the sub-application, and the corresponding sub-application can be reloaded under the condition of updating the page access identification, so that the corresponding page is cached again.

In one embodiment, the method further comprises: detecting whether the page access identifier is updated; and returning to the step of acquiring the page access identification of the page under the condition of determining the page access identification update so as to load the corresponding sub-application according to the re-acquired page access identification.

The processor may detect whether the page access identification is updated. Under the condition that the page access identification is updated, the method can return to the step of acquiring the page access identification of the page so as to reacquire the updated page access identification, and load the corresponding sub-application according to the reacquired page access identification.

Fig. 2 schematically shows a flow diagram of a method for page caching according to another embodiment of the application. As shown in fig. 2, in one embodiment, a method for page caching is provided, where a cache control device includes a configuration module, a cache module, and a loading module, where the cache module includes a sub-application cache module, and the loading module includes a sub-application loading module, and includes the following steps:

step 201, after detecting that a user accesses a page, a client sends a page access identifier of the page to a main application;

step 202, a configuration module sends sub-application configuration data to a main application, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier;

step 203, in the case that the main application determines that the target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data, the sub-application cache module sends a first history route identifier of the loaded sub-application to the main application;

Step 204, under the condition that the main application determines that the first historical route identifier has the identifier corresponding to the target sub-application, the sub-application loading module loads the sub-application corresponding to the page access identifier;

step 205, the main application determines a target page route identifier matched with a target sub-application identifier from the page route identifiers, and sends the target page route identifier to the sub-application;

in step 206, the sub-application caches the page according to the destination page route identification.

After detecting that the user accesses the page, the client may signal the user to access the page to the host application. After receiving the signal, the host application may send a signal to the client to obtain the page access identification of the page. The client may send a page access identification of the page to the host application. The main application may then send a request to the configuration module of the cache control device to obtain the sub-application configuration data. The configuration module may send the sub-application configuration data to the main application. The sub-application configuration data comprises a sub-application identifier and a page route identifier. Further, the sub-application configuration data may also include a deployment path for the sub-application.

In the case that the main application receives the sub-application configuration data and the page access identifier of the page, the main application may determine whether a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data. If the main application determines that the target sub-application identifier corresponding to the page access identifier does not exist in the sub-application configuration data, the main application can determine that the target sub-application identifier does not match with the page access identifier, and the target sub-application identifier is possibly the main application identifier. In the case that the main application determines that the sub-application configuration data includes the target sub-application identifier corresponding to the page access identifier, the main application may send a request for acquiring the first history route identifier of the loaded sub-application to a sub-application cache module of the cache control device. The sub-application caching module may send the first historical route identification of the loaded sub-application to the main application after receiving the request.

After the main application receives the first history route identifier of the loaded sub-application, whether the first history route identifier has the identifier of the target sub-application or not can be judged. And if the main application determines that the target sub-application identifier exists in the first historical route identifier, a loading instruction is sent to the sub-application loading module. The sub-application loading module may load a sub-application corresponding to the page access identifier. Specifically, the sub-application loading module may load the resource corresponding to the target sub-application identifier in the sub-application cache module, so as to load the sub-application corresponding to the page access identifier. After loading the corresponding sub-application, the main application may determine a target page route identifier matching the target sub-application identifier from the page route identifiers, and may send the target page route identifier to the sub-application. After receiving the destination page route identifier, the sub-application may cache the page according to the destination page route identifier.

According to the technical scheme, under the condition that state isolation exists between the main application and the sub-application, the main application can flexibly control the loading mode of the sub-application according to the sub-application configuration data and the first historical route identification of the loaded sub-application, the main application is prevented from repeatedly loading the same sub-application, the time for loading the same sub-application is greatly reduced, and the speed of a user for accessing a page is greatly improved.

In one embodiment, the caching module includes a page caching module, the loading module includes a page loading module, and the sub-application caches the page according to the target page identifier includes: the sub-application judges whether the page access identifier needs to be cached according to the target page route identifier; under the condition that the page access identification needs to be cached according to the target page route identification, the page cache module sends a second history route identification of the loaded page to the sub-application; the sub-application judges whether a page access identifier exists in the second historical route identifier; and under the condition that the sub-application determines that the page access identifier exists in the second historical route identifier, loading resource data corresponding to the page route identifier in the page buffer module through the page loading module so as to load the page.

The cache module further includes a page cache module. The page buffer module is used for buffering the resource data of the loaded page. The loading module comprises a page loading module. The page loading module is used for loading the pages in the sub-application. After the main application sends the target page route identifier to the sub-application, the sub-application can judge whether the page route identifier needs to be cached according to the target page identifier. If the sub-application determines that the page route identification does not need to be cached, the sub-application directly loads the page.

If the sub-application determines that the page route identification needs to be cached, a request for acquiring the second history route identification of the loaded page can be sent to a page cache module of the cache control device. The page cache module, upon receiving the request, may send a second historical route identification for the loaded page to the sub-application. The sub-application may further determine whether a page access identifier exists in the second historical route identifier. If the second historical route identifier has the page access identifier, the page loading module can load the resource data corresponding to the page route identifier in the page cache module so as to load the page.

In one embodiment, the method further comprises: under the condition that the sub-application determines that the page access identifier does not exist in the second historical route identifier, the sub-application loads the page for the first time; the client sends the second resource data of the page to the sub-application after receiving a second acquisition request of the second resource data; and the sub-application sends the second resource data to the page buffer module so that the page buffer module buffers the second resource data and updates the second historical route identification.

And under the condition that the sub-application determines that the page access identifier does not exist in the second historical route identifier, the sub-application loads the page for the first time. At this time, the sub-application may send a second acquisition request to acquire second resource data of the page to the client. The client may send the second resource data of the page to the sub-application after receiving the second acquisition request. After receiving the second resource data, the sub-application may send the second resource data to the page cache module, so that the page cache module caches the second resource data and updates the second historical route identifier.

In one embodiment, the method further comprises: before acquiring a page access identifier of a page, sub-application initial data sent by a client side is sent to a main application, wherein the sub-application initial data refers to initial data of a sub-application required to be mounted by the main application; the main application screens the initial data of the sub-application according to a preset rule, so that the screened initial data of the sub-application is used as the configuration data of the sub-application; the main application sends the sub-application configuration data to the configuration module to store the sub-application configuration data through the configuration module.

The host application may send a request to the client to obtain the initial data of the sub-application before obtaining the page access identification of the page. After receiving the request, the client may send the sub-application out-book data to the main application. The sub-application initial data refers to initial data of the sub-application required to be mounted by the main application. Then, the main application can screen the initial data of the sub-application according to a preset rule, so that the screened initial data of the sub-application is used as the configuration data of the sub-application. The main application may then send the sub-application configuration data to a configuration module of the cache control device to store the sub-application configuration data through the configuration module. The configuration module stores the configuration data of the sub-application, and when the main application is in state isolation with the sub-application, the loading mode of the sub-application can be controlled according to the configuration data of the sub-application.

In one embodiment, the method further comprises: the sub-application detects whether the route identification of the target page is updated or not; and returning to the step of judging whether the page access identifier needs to be cached according to the target page route identifier under the condition that the sub-application determines that the target page route identifier is updated, so that the sub-application rebuffers the corresponding page.

The sub-application may detect whether the destination page route identification is updated. If the sub-application determines that the target page route identifier is updated, the method can return to the step of judging whether the page access identifier needs to be cached according to the target page route identifier, so that the corresponding page is reloaded according to the second historical route identifier of the loaded page under the condition that the updated target page route identifier needs to be cached.

In one embodiment, the cache control device further includes a message module, and sending the destination page route identifier to the sub-application includes: and sending the target page route identification to the message module so as to send the target page route identification to the sub-application through the message module.

The cache control device also comprises a message module. The message module is used for communicating real-time messages between the main application and the sub-application. After the host application determines a target page route identification from the page route identifications that matches the target sub-application identifications, the host application may send the target page route identification to the message module. The message module may send the destination page route identification to the sub-application. A message communication channel is established between the message module and the sub-application, the page access identification can be obtained under the condition of being isolated from the state of the sub-application, and the corresponding sub-application can be reloaded under the condition of updating the page access identification, so that the corresponding page is cached again.

In one embodiment, the method further comprises: under the condition that the main application determines that the first historical route identifier does not exist in the target sub-application identifier, the main application loads the sub-application corresponding to the page access identifier for the first time; the method comprises the steps that a main application sends a first acquisition request to a client, wherein the first acquisition request is an acquisition request of first resource data of a sub-application corresponding to a page access identifier; the client sends first resource data of the sub-application corresponding to the page access identifier to the main application according to the first acquisition request; the main application sends the first resource data to the sub-application caching module so that the sub-application caching module caches the first resource data and updates the first historical route identification.

And under the condition that the main application determines that the first historical route identifier does not exist in the target sub-application identifier, the main application loads the sub-application corresponding to the page access identifier for the first time. And then, the main application sends a first acquisition request to the client, wherein the first acquisition request is an acquisition request of first resource data of the sub-application corresponding to the page access identifier. The client may send, according to the first acquisition request, first resource data of the sub-application corresponding to the page access identifier to the main application. The main application may then send the first resource data to the sub-application caching module, such that the sub-application caching module caches the first resource data and updates the first historical route identification. That is, when the sub-application is loaded for the first time, the main application may store the resource data of the sub-application loaded for the first time to the sub-application cache module of the cache control device. Therefore, after the main application is isolated from the sub-application state, the same sub-application can be loaded through the resource data of the loaded sub-application in the sub-application cache module, so that the repeated loading of the same sub-application after the sub-application is switched is avoided, and the loading efficiency and speed are improved.

In one embodiment, the method further comprises: the main application detects whether the page access identifier is updated; and returning to the step of sending the page access identification of the page to the main application by the client under the condition that the main application determines that the page access identification is updated, so as to load the corresponding sub-application according to the re-acquired page access identification.

The host application may detect whether the page access identification is updated. Under the condition that the main application determines that the page access identification is updated, the step of sending the page access identification of the page to the main application by the client can be returned to, so that the updated page access identification is obtained again, and the corresponding sub-application is loaded according to the obtained page access identification.

In one embodiment, as shown in FIG. 3, a flow diagram of yet another method for page caching is provided.

The main application can send the filtered sub-application data to the micro front-end cache control device, and can cache the filtered sub-application data to the micro front-end cache control device. The micro front-end cache control device and the sub-application can communicate. The main application can load the corresponding sub-application through the micro front-end cache control device and cache the resource data of the corresponding sub-application to the sub-application cache module of the micro front-end cache control device. After the main application loads the corresponding sub-application, the sub-application may cache the corresponding page.

In one embodiment, as shown in fig. 4, a block diagram of a micro front-end cache control device 400 is provided. The micro front-end cache control device 400 includes a configuration module 401, a message module 402, a loading module 403, and a cache module 404. The configuration module 401 is configured to perform configuration management on the sub-application identifier and the page route identifier when the main application loads the sub-application, and may also perform configuration management on the deployment path of the sub-application. The message module 402 is used for real-time message communication between the main application and the sub-application. The loading module 403 includes a sub-application loading module and a page loading module. The sub-application loading module is used for loading the sub-application. The page loading module is used for loading pages. The cache module 404 includes a sub-application cache module and a page cache module. The sub-application caching module is used for caching the loaded sub-application resource data. The page buffer module is used for buffering the loaded page resource data.

FIG. 5 schematically illustrates a timing diagram for sub-application loading according to an embodiment of the application.

The cache control device comprises a configuration module, a cache module, a loading module and a message module. The cache module comprises a sub-application cache module and a page cache module, and the loading module comprises a sub-application loading module and a page loading module. First, the main application data is initialized. Then, the main application transmits a request for acquiring the initial data of the sub-application to the client. After receiving the request, the client sends the sub-application initial data to the main application. After receiving the sub-application initial data, the main application may filter the sub-application initial data to obtain sub-application configuration data. The main application may then send the sub-application configuration data to a configuration module of the cache control device. The configuration module may store sub-application configuration data.

After the client receives the instruction of the user access operation, the access instruction may be sent to the host application. At this time, the host application may send an instruction to the client to acquire the page access identifier of the page. The client may send a page access identification to the host application according to the instruction. The main application may then send a request to the configuration module of the cache control device to obtain the sub-application configuration data. The configuration module of the cache control device may send the sub-application configuration data to the main application. After the main application receives the page access identifier and the sub-application configuration data, the main application may determine whether a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data. If the target sub-application identifier does not exist in the sub-application configuration data, the sub-application configuration data can be determined to be not matched with the page access identifier, and the page access identifier can be a main application identifier. If the target sub-application identifier exists in the sub-application configuration data, the main application further acquires the history route identifier of the loaded sub-application sent by the sub-application cache module of the cache control device.

In the case that the host application receives the history route identifier of the loaded sub-application, the host application may determine whether the target sub-application identifier exists in the history route identifier of the loaded sub-application. If the target sub-application identifier exists in the history route identifiers of the loaded sub-applications, the main application can send a first loading instruction to the cache control device. Further, the sub-application loading module included in the cache control device can load the sub-application corresponding to the page access identifier according to the first loading instruction. Specifically, the sub-application loading module loads resource data of the sub-application in the sub-application cache module to load the sub-application corresponding to the page access identifier. If the target sub-application identifier does not exist in the history route identifier of the loaded sub-application, the main application can load the sub-application corresponding to the page access identifier for the first time. At this time, the main application may transmit a request for acquiring the resource data of the sub-application to the client. The client may send the resource data of the sub-application to the main application. After receiving the resource data of the sub-application, the main application may send the resource data of the sub-application to the cache control device, so that the sub-application cache module of the cache control device stores the resource data of the sub-application.

FIG. 6 schematically illustrates a timing diagram of a page cache according to an embodiment of the application.

After the main application loads the corresponding sub-application, the target page route identification matched with the target sub-application identification can be screened out from the sub-application configuration data, and the screened target page route identification can be further sent to the message module of the cache control device. The message module may send the destination page route identification to the sub-application. The sub-application can judge whether the page access identifier needs to be cached according to the target page route identifier. In the case where the page access identification does not require caching, then the sub-application may load the page directly. In the case where the page access identifier needs to be cached, the sub-application may send a request to the cache control device to obtain the history route identifier of the loaded page. The page cache module of the cache control device may send the history route identification of the loaded page to the sub-application upon receiving the request.

The sub-application may further determine whether a page access identifier exists in the history route identifiers of the loaded pages. If the page access identifier exists in the history route identifier of the loaded page, the sub-application can send a second loading instruction to the cache control device. The page loading module of the cache control device may load the page according to the second loading instruction. Specifically, the page loading module may load resource data corresponding to the page route identifier in the page cache module to load the page. If the page access identifier does not exist in the history route identifier of the loaded page, the sub-application can load the page for the first time. At this point, the sub-application may send a request to the client to acquire the resource data for the page. The client may send the resource data for the page to the sub-application based on the request. The sub-application may send the received resource data of the page to the cache control device, so that the page cache module of the cache control device caches the resource data of the page.

In one embodiment, the host application may send configuration data to the configuration module. Specifically, the main application may send a request to the client to obtain sub-application data. After the main application obtains the sub-application data, the sub-application data can be screened, and the screened sub-application data is stored in the configuration module of the micro front end. The main application may send the cached sub-application resource data to the sub-application caching module. Specifically, after the user accesses the page, the host application may acquire an address input by the user in the client, and may determine the address as the current page routing address. And then, the main application can judge whether the current page route address matches the route identification of any sub-application according to the filtered sub-application data of the configuration module. If the current page route address bit matches the route identification of any sub-application, the route address can be directly matched in the main application. If the current page route address matches the route identifier of any sub-application, it can further judge whether the sub-application cache module contains the sub-application. If the sub-application cache module contains the sub-application, the sub-application can be loaded from the sub-application cache module through the sub-application loading module. If the sub-application cache module does not contain the sub-application, the main application loads the sub-application for the first time and can send a request to the client to acquire the resource data of the sub-application. After the main application obtains the resource data of the sub-application, the main application can send the resource data of the sub-application to the sub-application cache module.

After the main application loads the corresponding sub-application, the page route identification in the configuration module can be screened, and the screened page route identification refers to the page route identification which has response sub-application identification with the sub-application. The host application may send the filtered page route identification to the message module. The message module may send the filtered page route identification to the sub-application. The sub-application can judge whether the current page route address needs to be cached according to the screened page route identification. Under the condition that the current page routing address needs to be cached, the sub-application can judge whether the page caching module contains the current page routing address or not. If the page cache module contains the current page routing address, the sub-application can load the page from the page cache module through the page loading module. If the page cache module does not contain the current page routing address, the sub-application loads the page for the first time, sends a request to the client to acquire the resource data of the page, and caches the page to the page cache module. Further, the main application can detect whether the operation of the user for accessing the page is updated, and if so, the updated current page route address can be obtained again, so that the corresponding sub-application is reloaded. The sub-application can detect whether the screened page route identifier sent by the main application is updated, if so, whether the corresponding current page route address needs to be cached or not can be judged according to the updated page route identifier, and the corresponding page is further cached.

By the technical scheme, the loading mode and the page cache state of the sub-application can be flexibly controlled according to the configuration data after the main application is isolated from the sub-application state. And establishing a message channel between the main application and the sub-application, wherein the main application can acquire the cache state of the sub-application and the page thereof and issue and update the cache state of the page in real time. And the main application can cache the loaded sub-application, and the sub-application accessed by the user can be switched again to be opened quickly without waiting. The sub-application can cache the loaded page, and the sub-application page accessed by the user can be quickly opened without waiting. The scheme can greatly reduce the time of loading the sub-application and the page for multiple times and reduce the repeated loading of resources and data.

FIGS. 1-2 are flow diagrams of a method for page caching in one embodiment. It should be understood that, although the steps in the flowcharts of fig. 1-2 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 1-2 may include multiple sub-steps or phases that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or phases are performed necessarily occur sequentially, but may be performed alternately or alternately with at least a portion of the sub-steps or phases of other steps or other steps.

In one embodiment, a storage medium is provided having a program stored thereon that when executed by a processor implements the method for page caching described above.

In one embodiment, a processor is provided for running a program, where the program executes the method for page caching described above when running.

In one embodiment, an apparatus for page caching is provided, including the processor described above.

In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor a01, a network interface a02, a memory (not shown) and a database (not shown) connected by a system bus. Wherein the processor a01 of the computer device is adapted to provide computing and control capabilities. The memory of the computer device includes internal memory a03 and nonvolatile storage medium a04. The nonvolatile storage medium a04 stores an operating system B01, a computer program B02, and a database (not shown in the figure). The internal memory a03 provides an environment for the operation of the operating system B01 and the computer program B02 in the nonvolatile storage medium a04. The database of the computer device is used for storing data such as sub-application configuration data. The network interface a02 of the computer device is used for communication with an external terminal through a network connection. The computer program B02, when executed by the processor a01, implements a method for page caching.

It will be appreciated by those skilled in the art that the structure shown in FIG. 7 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

The embodiment of the application provides equipment, which comprises a processor, a memory and a program stored in the memory and capable of running on the processor, wherein the processor realizes the following steps when executing the program: acquiring a page access identifier of a page, wherein the page access identifier is sent after a client detects that a user accesses the page; acquiring sub-application configuration data sent by a configuration module, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier; under the condition that a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data, acquiring a first history route identifier of the loaded sub-application in a sub-application cache module; under the condition that a target sub-application identifier exists in the first historical route identifier, loading a sub-application corresponding to the page access identifier through a sub-application loading module; determining a target page route identifier matched with the target sub-application identifier from the page route identifiers; and sending the target page route identification to the sub-application so that the sub-application caches the page according to the target page identification.

In one embodiment, the method further comprises: before acquiring a page access identifier of a page, acquiring sub-application initial data sent by a client, wherein the sub-application initial data refers to initial data of a sub-application required to be mounted by a main application; screening the sub-application initial data according to a preset rule, and taking the screened sub-application initial data as sub-application configuration data; the sub-application configuration data is sent to the configuration module to store the sub-application configuration data by the configuration module.

In one embodiment, the method further comprises: under the condition that the first historical route identifier does not have the sub-application identifier corresponding to the target sub-application identifier, the sub-application corresponding to the page access identifier is loaded for the first time; acquiring first resource data of a sub-application corresponding to the page access identifier, wherein the first resource data is sent by a client after receiving a first acquisition request of the first resource data; and sending the first resource data to the sub-application caching module so that the sub-application caching module caches the first resource data and updates the first historical route identification.

In one embodiment, the cache control device further includes a message module that sends the destination page route identifier to the sub-application, so that the sub-application caches the page according to the destination page identifier, including: and sending the target page route identification to the message module, so that the target page route identification is sent to the sub-application through the message module, and the sub-application caches the page according to the target page identification.

In one embodiment, the method further comprises: detecting whether the page access identifier is updated; and returning to the step of acquiring the page access identification of the page under the condition of determining the page access identification update so as to load the corresponding sub-application according to the re-acquired page access identification.

The application also provides a computer program product adapted to perform a program initializing method steps for page caching when executed on a data processing device.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises an element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims (15)

1. The method for page caching is characterized by being applied to a main application, wherein a cache control device comprises a configuration module, a cache module and a loading module, the cache module comprises a sub-application cache module, the loading module comprises a sub-application loading module, and the method comprises the following steps:

acquiring a page access identifier of a page, wherein the page access identifier is sent after a client detects that a user accesses the page;

acquiring sub-application configuration data sent by the configuration module, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier;

under the condition that a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data, a first history route identifier of the loaded sub-application in the sub-application cache module is obtained;

loading a sub-application corresponding to the page access identifier through the sub-application loading module under the condition that the target sub-application identifier exists in the first historical route identifier;

Determining a target page route identifier matched with the target sub-application identifier from the page route identifiers;

and sending the target page route identification to a sub-application so that the sub-application caches the page according to the target page identification.

2. The method for page caching as defined in claim 1, further comprising:

before acquiring a page access identifier of a page, acquiring sub-application initial data sent by a client, wherein the sub-application initial data refers to initial data of a sub-application required to be mounted by the main application;

screening the sub-application initial data according to a preset rule to take the screened sub-application initial data as sub-application configuration data;

and sending the sub-application configuration data to the configuration module so as to store the sub-application configuration data through the configuration module.

3. The method for page caching as defined in claim 1, further comprising:

under the condition that the first historical route identifier does not exist in the target sub-application identifier, sub-applications corresponding to the page access identifier are loaded for the first time;

Acquiring first resource data of a sub-application corresponding to the page access identifier, wherein the first resource data is sent by the client after receiving a first acquisition request of the first resource data;

and sending the first resource data to the sub-application caching module so that the sub-application caching module caches the first resource data and updates the first historical route identification.

4. The method for page caching according to claim 1, wherein the cache control device further comprises a message module, and the sending the destination page route identifier to a sub-application, so that the sub-application caches the page according to the destination page identifier comprises:

and sending the target page route identification to the message module, so that the target page route identification is sent to the sub-application through the message module, and the sub-application caches the page according to the target page identification.

5. The method for page caching as defined in claim 1, further comprising:

detecting whether the page access identifier is updated;

and returning to the step of acquiring the page access identification of the page under the condition that the page access identification is updated, so as to load the corresponding sub-application according to the re-acquired page access identification.

6. A machine-readable storage medium having instructions stored thereon, which when executed by a processor cause the processor to be configured to perform the method for page caching according to any one of claims 1 to 5.

7. A processor configured to perform the method for page caching according to any one of claims 1 to 5.

8. A method for page caching, wherein a cache control device includes a configuration module, a cache module, and a loading module, the cache module includes a sub-application cache module, and the loading module includes a sub-application loading module, the method includes:

after detecting that a user accesses a page, a client sends a page access identifier of the page to a main application;

the configuration module sends sub-application configuration data to the main application, wherein the sub-application configuration data comprises a sub-application identifier and a page route identifier;

the sub-application caching module sends a first history route identifier of the loaded sub-application to the main application under the condition that the main application determines that a target sub-application identifier corresponding to the page access identifier exists in the sub-application configuration data;

Under the condition that the main application determines that the first historical route identifier exists in the target sub-application identifier, the sub-application loading module loads a sub-application corresponding to the page access identifier;

the main application determines a target page route identifier matched with the target sub-application identifier from the page route identifiers, and sends the target page route identifier to the sub-application;

and the sub-application caches the page according to the target page route identification.

9. The method for page caching as recited in claim 8, wherein the caching module comprises a page caching module, the loading module comprises a page loading module, and the sub-application caching the page according to the target page identification comprises:

the sub-application judges whether the page access identifier needs to be cached according to the target page route identifier;

under the condition that the page access identification needs to be cached according to the target page route identification, the page cache module sends a second historical route identification of the loaded page to the sub-application;

the sub-application judges whether the page access identifier exists in the second historical route identifier or not;

And under the condition that the sub-application determines that the page access identifier exists in the second historical route identifier, loading resource data corresponding to the page route identifier in the page cache module through the page loading module so as to load the page.

10. The method for page caching as recited in claim 9, further comprising:

under the condition that the sub-application determines that the page access identifier does not exist in the second historical route identifier, the sub-application loads the page for the first time;

the client sends the second resource data of the page to the sub-application after receiving a second acquisition request of the second resource data;

and the sub-application sends the second resource data to the page buffer module so that the page buffer module buffers the second resource data and updates the second history route identification.

11. The method for page caching as recited in claim 8, further comprising:

before acquiring a page access identifier of a page, sub-application initial data sent by the client side is sent to the main application, wherein the sub-application initial data refers to initial data of a sub-application required to be mounted by the main application;

The main application screens the sub-application initial data according to a preset rule to take the screened sub-application initial data as sub-application configuration data;

the main application sends the sub-application configuration data to the configuration module to store the sub-application configuration data through the configuration module.

12. The method for page caching as recited in claim 8, further comprising:

the sub-application detects whether the target page route identifier is updated or not;

and returning to the step of judging whether the page access identifier needs to be cached according to the target page route identifier under the condition that the sub-application determines that the target page route identifier is updated, so that the sub-application rebuffers the corresponding page.

13. The method for page caching as recited in claim 8, wherein the cache control device further comprises a message module, wherein sending the destination page route identification to a sub-application comprises:

and sending the target page route identification to the message module so as to send the target page route identification to the sub-application through the message module.

14. A machine-readable storage medium having instructions stored thereon, which when executed by a processor cause the processor to be configured to perform the method for page caching according to any of claims 8 to 13.

15. A processor configured to perform the method for page caching according to any one of claims 8 to 13.