Applet access method, device and storage medium

Abstract

This application provides a method, device, and storage medium for accessing a mini-program. The method includes: upon detecting an access request for a target mini-program, determining whether the underlying resource files of the target mini-program are cached; if the underlying resource files of the target mini-program are not cached, obtaining the corresponding underlying resource files from the network based on the resource network path of the underlying resource files of the target mini-program, loading the obtained underlying resource files, and caching the obtained underlying resource files; if the underlying resource files of the target mini-program are cached, loading the cached underlying resource files of the target mini-program. This improves the efficiency of mini-program access.

Description

Technical Field

[0001] This application relates to the field of information technology, and in particular to a method, device and storage medium for accessing mini-programs. Background Technology

[0002] Mini-programs are applications that can be used without downloading or installing. For developers, the development threshold for mini-programs is relatively low, and they can meet the needs of simple, basic applications. For users, they can save time and phone memory.

[0003] When an application on a terminal device launches a mini-program, it needs to obtain the underlying resource files from the network based on the resource network path of the underlying resource files and load them. In poor network conditions, this can easily lead to loading lag issues for mini-programs, especially for large H5 mini-programs, where the lag issues will be more pronounced. Summary of the Invention

[0004] This application provides a method, device, and storage medium for accessing mini-programs, so as to achieve efficient access to mini-programs.

[0005] The first aspect of this application provides a method for accessing a mini-program, including:

[0006] Upon detecting an access request for the target mini-program, determine whether the underlying resource files of the target mini-program are cached;

[0007] If the underlying resource files of the target mini-program are not cached, the corresponding underlying resource files are obtained from the network according to the resource network path of the underlying resource files of the target mini-program, the obtained underlying resource files are loaded, and the obtained underlying resource files are cached.

[0008] If the underlying resource files of the target mini-program are cached, the cached underlying resource files of the target mini-program are loaded.

[0009] A second aspect of this application provides a server, wherein the server includes:

[0010] One or more processors;

[0011] Machine-readable storage medium for storing one or more computer-readable instructions.

[0012] When the one or more computer-readable instructions are executed by the one or more processors, the one or more processors cause the one or more processors to perform the method as described in the first aspect of this application.

[0013] A third aspect of this application provides a machine-readable storage medium having a program stored thereon that, when executed by a processor, implements the method described in the first aspect of this application.

[0014] The embodiments of this application have the following beneficial effects:

[0015] In this embodiment, upon detecting an access request for a target mini-program, it is determined whether the underlying resource files of the target mini-program are cached. If the underlying resource files of the target mini-program are not cached, the corresponding underlying resource files are obtained from the network based on the resource network path of the underlying resource files of the target mini-program, the obtained underlying resource files are loaded, and the obtained underlying resource files are cached. If the underlying resource files of the target mini-program are cached, the cached underlying resource files of the target mini-program are loaded. By caching the underlying resource files obtained from the network, when it is necessary to load the cached underlying resource files again, it is not necessary to obtain the underlying resource files from the network; instead, the cached underlying resource files can be obtained, thereby improving the loading efficiency of the underlying resource files and reducing the probability of mini-program loading lag. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating a method for accessing a mini-program according to an embodiment of this application;

[0018] Figure 2 This is a structural block diagram of a server according to an embodiment of this application. Detailed Implementation

[0019] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0020] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0021] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various devices, this information should not be limited to these terms. These terms are only used to distinguish devices of the same type from one another. For example, without departing from the scope of this application, a first device may also be referred to as a second device, and similarly, a second device may also be referred to as a first device. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0022] The message push method of this application embodiment will be described in more detail below, but it should not be limited thereto.

[0023] The first aspect of this application provides a method for accessing a mini-program, see [link / reference]. Figure 1 The method to access this mini-program includes the following steps:

[0024] It should be noted that the execution subject of the mini-program access method provided in the first aspect of this application can be a terminal device, such as a smartphone, tablet, or smart wearable device.

[0025] S100: Upon detecting an access request for the target mini-program, determine whether the underlying resource files of the target mini-program are cached. If yes, proceed to step S120; otherwise, proceed to step S110.

[0026] For example, the target mini-program mentioned above does not specifically refer to a particular mini-program, but can refer to any mini-program that is allowed to be launched in any application running on the terminal device.

[0027] In this embodiment of the application, in order to improve the loading efficiency of the mini program and reduce the probability of loading lag, when loading the underlying resource files of the mini program, the underlying resource files of the mini program obtained from the network can be cached. Then, when it is necessary to load the underlying resource files again, the underlying resource files can be obtained from the cache instead of obtaining them from the network again.

[0028] Accordingly, when an access request for a target mini-program is detected, for example, when a user opens the target mini-program on a mobile phone through an application, it can be determined whether the underlying resource files of the target mini-program are cached.

[0029] For example, the underlying resource files mentioned above may include, but are not limited to, HTML (Hyper Text Markup Language) files, JS (JavaScript, a programming language) files, and images.

[0030] Step S110: Based on the resource network path of the underlying resource file of the target mini-program, obtain the corresponding underlying resource file from the network, load the obtained underlying resource file, and cache the obtained underlying resource file.

[0031] In this embodiment of the application, for any underlying resource file of the target mini-program, if it is determined that the underlying resource file is not cached, the underlying resource file can be obtained from the network end based on the resource network path of the underlying resource file.

[0032] For example, once the underlying resource file is obtained, it can be loaded to enable the target mini-program to run.

[0033] On the other hand, the underlying resource file obtained can be cached.

[0034] Step S120: Load the underlying resource files corresponding to the cached resource network paths.

[0035] In this embodiment of the application, for any underlying resource file of the target mini-program, if it is determined that the underlying resource file is cached, it is not necessary to obtain the underlying resource file from the network. Instead, the cached underlying resource file can be obtained and loaded to improve the loading efficiency of the underlying resource file.

[0036] It can be seen that, in Figure 1 In the illustrated method flow, upon detecting an access request for the target mini-program, it is determined whether the underlying resource files of the target mini-program are cached. If the underlying resource files of the target mini-program are not cached, the corresponding underlying resource files are retrieved from the network based on the resource network path of the target mini-program's underlying resource files, the retrieved underlying resource files are loaded, and the retrieved underlying resource files are cached. If the underlying resource files of the target mini-program are cached, the cached underlying resource files of the target mini-program are loaded. By caching the underlying resource files retrieved from the network, when it is necessary to load the cached underlying resource files again, it is not necessary to retrieve the underlying resource files from the network; instead, the cached underlying resource files can be retrieved, thereby improving the loading efficiency of the underlying resource files and reducing the probability of mini-program loading lag.

[0037] In some embodiments, caching the obtained underlying resource files may include:

[0038] For any underlying resource file obtained, the underlying resource file and its resource network path are associated and cached.

[0039] The determination of whether the underlying resource files of the target mini-program are cached may include:

[0040] For any underlying resource file, query whether the underlying resource file is cached based on its resource network path.

[0041] For example, considering that different mini-programs may have the same underlying resource files that need to be loaded, such as mini-program A needing to load underlying resource files 1 to 3, and mini-program B needing to load underlying resource files 3 to 5, that is, both mini-program A and mini-program B need to load underlying resource file 3, in order to make fuller use of the cached underlying resource files, when caching the underlying resource files, each underlying resource file can be associated with the resource network path of the underlying resource file, such as the URL (Uniform Resource Locator).

[0042] Accordingly, when an access request for a target mini-program is detected, for any underlying resource file that the target mini-program needs to load, it can be queried whether the underlying resource file is cached based on the resource network path of the underlying resource file.

[0043] In one example, the above-mentioned association caching of the underlying resource file and its resource network path can include:

[0044] The underlying resource file is cached using the hash value of its resource network path as the key.

[0045] For example, considering that the resource network path of the underlying resource file is usually quite long, caching it will consume a lot of cache space and the comparison efficiency will be low, in order to reduce the consumption of storage resources and improve the comparison efficiency, when associating and caching the resource network paths of the underlying resource files, the resource network path of the underlying resource file can be hashed to obtain the hash value of the resource network path of the underlying resource file, and the underlying resource file can be cached using the hash value as the key.

[0046] Accordingly, when an access request for a target mini-program is detected, for any underlying resource file of the target mini-program, the hash value of the underlying resource file can be used to query whether the corresponding underlying resource file is cached.

[0047] In some embodiments, caching the obtained underlying resource files may include:

[0048] The underlying resource files of the target mini-program are associated with and cached with the identification information of the target mini-program;

[0049] The determination of whether the underlying resource files of the target mini-program are cached may include:

[0050] Based on the identifier information of the target mini-program, check whether the corresponding underlying resource files are cached.

[0051] For example, in order to further improve the loading efficiency of mini programs, for any mini program, after obtaining all the underlying resource files of the mini program from the network, all the underlying resource files of the mini program and the identification information of the mini program (such as the ID name of the mini program) can be associated and stored. When the mini program is launched later, such as when the mini program is launched again through the same application, or when the mini program is launched through other applications, all the underlying resource files required for the loading of the mini program can be obtained.

[0052] For example, suppose a user opens mini-program A on their phone through application APP1. If mini-program A is not cached, the corresponding underlying resource files can be obtained from the network based on the network resource paths of each underlying resource file of mini-program A, and the identification information of mini-program A can be associated with and cached with all the underlying resource files of mini-program A. When the user opens mini-program A again on their phone through application APP2, the cached underlying resource files can be found based on the identification information of mini-program A, so that it is not necessary to obtain the underlying resource files from the network again.

[0053] Accordingly, when caching the underlying resource files of the target mini-program, the underlying resource files of the target mini-program can be associated with the identification information of the target mini-program for caching.

[0054] When determining whether the underlying resource files of the target mini-program are cached, the underlying resource files of the target mini-program can be queried based on the identification information of the target mini-program.

[0055] In one example, the above-mentioned association and caching of the underlying resource files of the target mini-program with the identification information of the target mini-program may include:

[0056] The underlying resource files of the target mini-program are cached using the hash value of the target mini-program's identifier information as the key.

[0057] For example, when caching the underlying resource files of the target mini-program, the hash value of the target mini-program's identification information can be used as the key to cache the underlying resource files of the target mini-program.

[0058] Accordingly, when determining whether the underlying resource files of the target mini-program are cached, the identification information of the target mini-program can be hashed to obtain the hash value of the identification information of the target mini-program, and the corresponding underlying resource files can be queried based on the hash value.

[0059] It should be noted that, in the embodiments of this application, for any mini-program, the association caching of the mini-program's identification information with the mini-program's underlying resource files and the association caching of the resource network paths of the mini-program's underlying resource files with the underlying resource files can be performed concurrently.

[0060] Accordingly, when determining whether the underlying resource files of the target mini-program are cached, the underlying resource files (i.e. all underlying resource files) of the target mini-program can be queried based on the identification information of the target mini-program. If no cached underlying resource files are found based on the identification information of the target mini-program, for any underlying resource file that the target mini-program needs to load, the corresponding underlying resource file can be queried based on the resource network path of the underlying resource file.

[0061] Furthermore, for any mini-program, when caching the association between the mini-program's identification information and its underlying resource files, and when caching the association between the resource network path of the mini-program's underlying resource files and the underlying resource files themselves, the same underlying resource file does not need to be cached repeatedly.

[0062] For example, suppose that Mini Program A needs to load underlying resource files 1 to 3 (assuming the resource network paths are url1 to 3 respectively), and when caching the underlying resource files of Mini Program A, the cache address of underlying resource file 1 is add1, the cache address of underlying resource file 2 is add2, and the cache address of underlying resource file 3 is add3. Then, on the one hand, the correspondence between the identification information of Mini Program A (such as the hash value of the identification information) and add1 to 3 can be recorded; on the other hand, the correspondence between url1 and add1, url2 and add2, and url3 and add3 can be recorded.

[0063] When a user launches mini-program A on their phone, they can retrieve all the underlying resource files required by the cached mini-program A based on the identification information of mini-program A. When a user launches mini-program B on their phone, and the underlying resource files required by mini-program B include underlying resource files 3 to 5, they can retrieve the cached underlying resource file 3 based on the resource network path URL 3 of underlying resource file 3.

[0064] In some embodiments, when the underlying resource files of the target mini-program are cached, before loading the cached underlying resource files of the target mini-program, the following may be included:

[0065] For any underlying resource file of the cached target mini-program, obtain the network version information of the underlying resource file, and determine whether the version information of the cached underlying resource file is consistent with the network version information.

[0066] If the version information of the cached underlying resource file is consistent with the version information on the network, then the operation of loading the cached underlying resource file will be performed.

[0067] For example, considering that the underlying resource files that the mini program needs to load may be updated in real-world scenarios, in order to ensure the accuracy of the underlying resource files loaded by the mini program, if the underlying resource files of the mini program are cached, before loading the cached underlying resource files, it is necessary to ensure that the version information of the cached underlying resource files is consistent with the version information of the underlying resource files on the network.

[0068] If the version information of the cached underlying resource file is consistent with the version information on the network, it is not necessary to obtain the underlying resource file from the network; instead, the cached underlying resource file can be loaded.

[0069] In one example, the method for accessing a mini-program provided in this application embodiment may further include:

[0070] If the version information of the underlying resource file in the cache is inconsistent with the version information on the network, the underlying resource file is obtained from the network according to the resource network path of the underlying resource file, the obtained underlying resource file is loaded, and the cached underlying resource file is updated.

[0071] For example, for any underlying resource file, if it is determined that the underlying resource file exists in the cache, but the version information of the cached underlying resource file is inconsistent with the version information on the network, the underlying resource file can be obtained from the network based on the resource network path of the underlying resource file. On the one hand, the obtained underlying resource file can be loaded to enable the normal operation of the target mini-program; on the other hand, the cached underlying resource file can be updated based on the underlying resource file obtained from the network to ensure that the version information of the cached underlying resource file is consistent with the version information of the underlying resource file on the network.

[0072] For example, the inconsistency between the version information of the underlying resource file cached above and the version information on the network side includes the network side version information being updated (i.e., the underlying resource file has been updated), or the network side version information being older (i.e., the underlying resource file has been rolled back).

[0073] In some embodiments, after caching the obtained underlying resource files as described above, the method may further include:

[0074] For any cached underlying resource file, periodically obtain the network version information of the underlying resource file and determine whether the version information of the cached underlying resource file is consistent with the network version information.

[0075] If the version information of the cached underlying resource file is inconsistent with the version information on the network, the underlying resource file is retrieved from the network based on the resource network path of the underlying resource file, and the cached underlying resource file is updated.

[0076] For example, in order to improve the efficiency of loading underlying resource files when the version information of the underlying resource files changes, for any cached underlying resource file, the network version information of the underlying resource file can be obtained periodically (e.g., periodically), and it can be determined whether the version information of the cached underlying resource file is consistent with the network version information.

[0077] If the version information of the cached underlying resource file is inconsistent with the version information on the network, the underlying resource file can be retrieved from the network based on its resource network path, and the cached underlying resource file can be updated. This allows for pre-updating of the version information of the cached underlying resource file, eliminating the need for real-time version updates of the underlying resource file while it is cached, thus improving the efficiency of loading the underlying resource file.

[0078] To enable those skilled in the art to better understand the technical solutions provided in the embodiments of this application, the technical solutions provided in the embodiments of this application are described below with reference to specific examples.

[0079] In this embodiment, assuming a user opens mini-program A on a mobile phone through APP1, and the mobile phone detects an access request for mini-program A, the mobile phone can query whether the underlying resource files of mini-program A are cached based on the ID name of mini-program A.

[0080] Suppose that the underlying resource files of mini program A include underlying resource files 1 to 3, and the cached underlying resource files 1 to 3 are not found based on the ID name of mini program A.

[0081] The mobile phone can determine whether the corresponding underlying resource file is cached based on the resource network paths of underlying resource files 1 to 3 (assuming they are URLs 1 to 3 respectively).

[0082] Suppose that no cached underlying resource file is found based on the resource network path of each underlying resource file.

[0083] In this case, the mobile phone can obtain the underlying resource files 1 to 3 from the network according to the resource network paths of the underlying resource files 1 to 3 respectively. On the one hand, the mobile phone can associate and cache the ID name of the mini program A (assuming it is id1) with the underlying resource files 1 to 3; on the other hand, it can associate and cache url1 with the underlying resource file 1, url2 with the underlying resource file 2, and url3 with the underlying resource file 3.

[0084] After launching the aforementioned mini-program A, if the user opens mini-program A again on the phone via APP2, the phone detects an access request for mini-program A. In this case, the phone can query whether the underlying resource files of mini-program A are cached based on the ID name of mini-program A, and determine that underlying resource files 1 to 3 are cached.

[0085] The mobile phone can obtain the network version information of the underlying resource files 1 to 3 from the network based on the resource network paths (url1 to 3) of the underlying resource files 1 to 3 respectively, and compare the network version information of the underlying resource files 1 to 3 with the cached version information of the underlying resource files 1 to 3. If they match, the cached underlying resource files 1 to 3 are loaded, thereby realizing the ultra-fast access of the mini program across hosts.

[0086] Suppose a user opens mini-program 2 on their phone through APP1 (assuming that the underlying resource files of mini-program 2 include underlying resource files 3 to 5, and the resource network paths are URLs 3 to 5 respectively). When the phone detects an access request for mini-program 2, it can query whether the corresponding underlying resource files are cached based on the ID name of mini-program 2.

[0087] If no corresponding underlying resource file is found in the cache based on the ID name of Mini Program 2, the mobile phone can query whether the corresponding underlying resource file is cached based on URLs 3 to 5 respectively. The query results show that the corresponding underlying resource file is found in the cache based on URL 3 (i.e., underlying resource file 3), while no corresponding underlying resource file is found in the cache based on URLs 4 to 5 (i.e., underlying resource files 4 to 5).

[0088] For underlying resource file 3, the mobile phone can obtain the network version information of underlying resource file 3 based on URL 3, and compare whether the cached version information of underlying resource file 3 is consistent with the network version information. If the version information is consistent, the cached underlying resource file 3 can be obtained.

[0089] For underlying resource files 4 to 5, the mobile phone can obtain underlying resource files 4 to 5 from the network based on URLs 4 to 5, and perform associated caching of URL 4 and underlying resource file 4, and associated caching of URL 5 and underlying resource file 5 respectively.

[0090] If the underlying resource files 3 to 5 are obtained, the ID name of Mini Program B can also be associated with and cached with the underlying resource files 3 to 5.

[0091] This application also provides a server, wherein the server includes:

[0092] One or more processors;

[0093] Machine-readable storage medium for storing one or more computer-readable instructions.

[0094] When the one or more computer-readable instructions are executed by the one or more processors, the one or more processors cause the one or more processors to perform the method as described in the first aspect of the present application.

[0095] The embodiments of the mini-program access method described above in this application can be applied to a server. Taking software implementation as an example, the processor of the server loads the corresponding computer program instructions from the non-volatile memory into memory and executes them to implement the embodiments of the mini-program access method of this application. From a hardware perspective, such as Figure 2 As shown, Figure 2 This is a hardware structure diagram of a server illustrated in an exemplary embodiment of this application, except... Figure 2 In addition to the processor 210, memory 230, interface 220, and non-volatile memory 240 shown, the server may also include other hardware depending on the actual function of the server, which will not be described in detail here.

[0096] This application also provides a machine-readable storage medium having a program stored thereon, which, when executed by a processor, implements the applet access method as described in any of the foregoing embodiments.

[0097] This application may take the form of a computer program product implemented on one or more storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing program code. Machine-readable storage media include permanent and non-permanent, removable and non-removable media, which can be used to store information by any method or technology. The information may be computer-readable instructions, data structures, program modules, or other data. Examples of machine-readable storage media 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information that can be accessed by a computing device.

[0098] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. An applet access method characterized by comprising: The method comprises: In the case of detecting an access request for a target applet, according to the identification information of the target applet, it is inquired whether all underlying resource files associated with the identification information are cached; In the case of inquiring all underlying resource files cached according to the identification information, all underlying resource files cached of the target applet are loaded; In the case of not inquiring all underlying resource files cached according to the identification information, the following steps are performed: For each underlying resource file in the target applet, according to the resource network path of the underlying resource file, it is inquired whether the underlying resource file is cached; If the underlying resource file is not cached according to the resource network path of the underlying resource file, the underlying resource file is obtained from the network, and the obtained underlying resource file is associated with the resource network path of the underlying resource file and cached; If the underlying resource file is cached according to the resource network path of the underlying resource file, the underlying resource file is obtained from the cache; In the case of obtaining all underlying resource files included in the target applet, all underlying resource files are loaded, and all underlying resource files of the target applet are associated with the identification information of the target applet and cached.

2. The method of claim 1, wherein, The obtained underlying resource file is associated with the resource network path of the underlying resource file and cached, which comprises: The hash value of the resource network path of the underlying resource file is taken as the key, and the underlying resource file is cached.

3. The method of claim 1, wherein, The identification information of the target applet is taken as the key, and the underlying resource file of the target applet is cached. Before loading the cached underlying resource file in the case of inquiring all underlying resource files cached according to the identification information, or in the case of inquiring the underlying resource file cached according to the resource network path of the underlying resource file, the following steps are further included:

4. The method of claim 1, wherein, For any underlying resource file of the target applet cached, the network end version information of the underlying resource file is obtained, and it is determined whether the version information of the cached underlying resource file is consistent with the network end version information; In the case of the version information of the cached underlying resource file being consistent with the network end version information, it is determined to perform the operation of loading the cached underlying resource file. The method further comprises:

5. The method of claim 4, wherein, In the case of the version information of the cached underlying resource file being inconsistent with the network end version information, the underlying resource file is obtained from the network end according to the resource network path of the underlying resource file, the obtained underlying resource file is loaded, and the cached underlying resource file is updated. After the obtained underlying resource file is associated with the resource network path of the underlying resource file and cached, the following steps are further included:

6. The method of any one of claims 1, wherein, ​ For any underlying resource file cached, network-side version information of the underlying resource file is acquired in a timely manner, and it is determined whether the version information of the cached underlying resource file is consistent with the network-side version information; In a case where it is determined that the version information of the cached underlying resource file is inconsistent with the network-side version information, the underlying resource file is acquired from the network side according to a resource network path of the underlying resource file, and the cached underlying resource file is updated.

7. A server, wherein, The server comprises: one or more processors; a machine-readable storage medium for storing one or more computer-readable instructions, when the one or more computer-readable instructions are executed by the one or more processors, the one or more processors implement the method of any one of claims 1-6.

8. A machine-readable storage medium having stored thereon a program which, when executed by a processor, implements the method of any one of claims 1-6.

Images