CN107729352A - page resource loading method and terminal device - Google Patents

Abstract

The invention provides a kind of page resource loading method and terminal device, suitable for Mobile solution technical field, this method includes：When page load events are triggered, page load request is intercepted, and obtains the page address entrained by the page load request；Based on website corresponding to the page address, it is determined that the page resource plug-in unit with the site match, the page resource plug-in unit is pre-stored within the installation kit of application program；The page resource plug-in unit is run, with multiple static cache resources under the website that is locally stored；In the application program, according to default network view, the static cache resource matched with the page address is loaded.This invention ensures that even Hybrid App are first under the situation of loading page resource, also can be from local quick loading page resource, so as to reduce the number to second server requests for page resource, the loading for greatly reducing page resource takes, and improves Hybrid App performance.

Description

Page resource loading method and terminal device

technical field

The invention belongs to the technical field of mobile applications, and in particular relates to a page resource loading method and a terminal device.

Background technique

With the continuous updating of technology, mobile terminal applications are gradually developing along the direction of localized applications (NativeApp), to WEB-based applications (Web App), and then to hybrid applications (Hybrid APP). Hybrid App is an application written based on web page language and programming language. From the user's point of view, the interface of the Hybrid App will be similar to that of the Native App, but in fact, the mobile application displays pages based on HTML5.

During the development of the Hybrid App, if the HTML5 pages are not fully optimized, and the network environment is poor, when the user uses the Hybrid App and loads page resources for the first time, it often takes a lot of time to obtain page resource. According to the statistics, under the network environment of 3g or 2g, the page resource consumes even more than one minute when the page resources are loaded for the first time, which leads to the extremely low performance of the hybrid app.

Contents of the invention

In view of this, the embodiments of the present invention provide a method for loading page resources and a terminal device, so as to solve the problem in the prior art that the Hybrid App takes a lot of time when loading page resources for the first time.

The first aspect of the embodiments of the present invention provides a page resource loading method, including:

When the page loading event is triggered, the page loading request is intercepted, and the page address carried by the page loading request is obtained;

Based on the site corresponding to the page address, determine a page resource plug-in that matches the site, where the page resource plug-in is pre-stored in the installation package of the application;

Running the page resource plug-in to obtain a plurality of static cache resources stored locally under the site;

In the application program, the static cache resource matching the page address is loaded according to a preset network view.

The second aspect of the embodiments of the present invention provides a terminal device, including a memory and a processor, the memory stores a computer program that can run on the processor, and it is characterized in that the processor executes the When a computer program is implemented, the following steps are implemented:

When the page loading event is triggered, the page loading request is intercepted, and the page address carried by the page loading request is obtained;

Based on the site corresponding to the page address, determine a page resource plug-in that matches the site, where the page resource plug-in is pre-stored in the installation package of the application;

Running the page resource plug-in to obtain a plurality of static cache resources stored locally under the site;

In the application program, the static cache resource matching the page address is loaded according to a preset network view.

A third aspect of the embodiments of the present invention provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

When the page loading event is triggered, the page loading request is intercepted, and the page address carried by the page loading request is obtained;

Based on the site corresponding to the page address, determine a page resource plug-in that matches the site, where the page resource plug-in is pre-stored in the installation package of the application;

Running the page resource plug-in to obtain a plurality of static cache resources stored locally under the site;

In the application program, the static cache resource matching the page address is loaded according to a preset network view.

In the embodiment of the present invention, by storing page resource plug-ins matching multiple sites in the application installation package of the Hybrid App, and making the Hybrid App run the locally stored page resource plug-ins when intercepting a page loading request, to Loading the static cache resources that match the page loading request ensures that the Hybrid App can quickly load the page resources locally even when the page resources are loaded for the first time, thereby reducing the number of requests for page resources from the remote server and greatly reducing the It reduces the time-consuming loading of page resources, thus improving the performance of the Hybrid App.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the accompanying drawings that need to be used in the descriptions of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only of the present invention. For some embodiments, those of ordinary skill in the art can also obtain other drawings based on these drawings without paying creative efforts.

Fig. 1 is the implementation flowchart of the page resource loading method provided by the embodiment of the present invention;

Fig. 2 is an implementation flow chart of a page resource loading method provided by another embodiment of the present invention;

Fig. 3 is a flow chart of realizing a page resource loading method provided by another embodiment of the present invention;

FIG. 4 is a specific implementation flowchart of the page resource loading method S104 provided by the embodiment of the present invention;

Fig. 5 is a structural block diagram of a page resource loading device provided by an embodiment of the present invention;

Fig. 6 is a structural block diagram of a page resource loading device provided by another embodiment of the present invention;

Fig. 7 is a structural block diagram of a page resource loading device provided by another embodiment of the present invention;

Fig. 8 is a schematic diagram of a terminal device provided by an embodiment of the present invention.

detailed description

In the following description, specific details such as specific system structures and technologies are presented for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of the present invention. It will be apparent, however, to one skilled in the art that the invention may be practiced in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

In each embodiment of the present invention, the execution subject of the process is an application program running on a mobile terminal, referred to as a mobile application. This mobile application is a Hybrid App.

In order to illustrate the technical solutions of the present invention, specific examples are used below to illustrate.

Fig. 1 shows the implementation process of the page resource loading method provided by the embodiment of the present invention, and the method process includes steps S101 to S104. The specific implementation principle of each step is as follows.

S101: When a page loading event is triggered, intercept the page loading request, and acquire the page address carried in the page loading request.

The moment when the mobile application loads page resources includes the moment when the mobile application is started and the moment when a resource selection instruction from the user is received during the running of the mobile application. In the above case, the page load event is fired. At this point, the mobile application generates a page load request. When the interceptor preset in the mobile application detects the page loading request, it will intercept and capture the page loading request, so that the page loading request cannot reach its destination address normally, that is, the page loading request cannot be sent to the remote server and Could not request to load page resource on remote network.

The page loading request intercepted at the current moment is parsed to extract the page address carried in the page loading request. The aforementioned page address may be, for example, a URL (Uniform Resource Locator, Uniform Resource Locator) address of a page resource stored on a remote server. The page address can reflect information such as the network transmission protocol, IP address, domain name address, path, and resource file name.

Exemplarily, the page address carried by the intercepted page loading request may be: local://www.abc.com/item/url/110640.

Preferably, the network transmission protocol corresponding to the native page resource of the mobile application is usually the file protocol. Since the file protocol cannot be identified and intercepted, during the development process of the mobile application, the network transmission protocol corresponding to the native page resource is uniformly changed to local protocol. The page loading request is intercepted only when it is detected that the protocol of the page address carried in the page loading request is the local protocol.

S102: Based on the site corresponding to the page address, determine a page resource plug-in that matches the site, where the page resource plug-in is pre-stored in an installation package of the application program.

A site represents a virtual directory that organizes, maintains, and manages resources for multiple pages. According to the page address obtained in S101 above, the IP address part or the domain name address part in the page address is determined as the site corresponding to the page address.

For example, in the above page address http://www.abc.com/item/url/110640, the resolved domain name address is "www.abc.com", so the site corresponding to the page address is www.abc.com site.

In the embodiment of the present invention, before the mobile application is started, the mobile application needs to be installed based on the pre-downloaded installation package of the mobile application. In the downloaded installation package, page resource plug-ins of multiple sites are stored. Specifically, before releasing the installation package of the mobile application, the page resources of each site related to the mobile application will be integrated into a hfcache plug-in, and packaged into the installation package of the mobile application with the hfcache plug-in.

After the mobile application is successfully installed, obtain each page resource plug-in from the installation package. According to the plug-in name of each page resource plug-in and the site corresponding to the above page loading request, the page resource plug-in matching the site is determined from the page resource plug-ins integrated in the installation package.

S103: Run the page resource plug-in to obtain a plurality of static cache resources stored locally under the site.

When each hfcache plug-in is running, it will call a compressed package and a cache file list corresponding to the hfcache plug-in. The file format of the above compressed package includes but not limited to .zip format or .rar format. The compressed package contains various static cache resources of the site, such as js files, css files, pictures and audio files in the site. The cache file list is used to record the resource names of each static cache resource in the compressed package and the MD5 value corresponding to each static cache resource. When publishing each static cache resource, its MD5 value will be calculated by a preset algorithm. In the process of integrating static cache resources into the hfcache plug-in, its MD5 value will be recorded in the cache file list corresponding to the hfcache plug-in.

Decompress the compressed package corresponding to the hfcache plug-in to obtain the static cache resources under each storage path.

S104: In the application program, load the static cache resource matching the page address according to a preset network view.

From the page address carried in the page loading request, the resource path and the resource file name of the page resource to be loaded by the current mobile application are parsed out. Among the decompressed static cache resources, determine the static cache resource matching the resource path and resource file name.

WebView is a control based on the webkit engine and used to display web pages. In the embodiment of the present invention, the determined static cache resource is parsed through the preset WebView inside the mobile application to generate a corresponding Web page, thereby realizing the display of the page resource required by the page loading request.

In the embodiment of the present invention, by storing page resource plug-ins matching multiple sites in the application installation package of the Hybrid App, and making the Hybrid App decompress the locally stored page resource plug-ins when intercepting a page loading request, to Loading the static cache resources that match the page loading request ensures that the Hybrid App can quickly load the page resources locally even when the page resources are loaded for the first time, thereby reducing the number of requests for page resources from the remote server and greatly reducing the It reduces the time-consuming loading of page resources, thus improving the performance of the Hybrid App.

As another embodiment of the present invention, as shown in FIG. 2, after the above S104, it also includes:

S105: Send a plug-in update detection request to the first server every preset time interval.

The static cache resources of different sites are usually maintained and updated by different teams. In order to facilitate the mobile application to update the static cache resources of each site stored locally, the embodiment of the present invention provides a static cache resource release platform, and each team logs in through its login account After the static cache resource is published on the platform, the updated static cache resource can be packaged and uploaded. After the page resource plug-in is uploaded to the static cache resource publishing platform, the update release of the page resource plug-in is completed. For ease of understanding and to distinguish it from the remote server mentioned below, the static cache resource distribution platform is referred to as the first server.

The mobile application sends a plug-in update detection request to the first server every preset time interval, so as to detect whether the locally stored static cache resource is updated at the current moment.

As an embodiment of the present invention, the above S105 specifically includes:

Send a plug-in update detection request to the first server every preset time interval, the plug-in update detection request includes the identification number of the page resource plug-in, so that the first server is bound to the identification number From the plug-in resource page of , extract the static cache resource published at the current moment, and make the first server return the first cache file list related to the static cache resource.

In the embodiment of the present invention, each page resource plug-in stored locally is pre-allocated with an identification number, that is, an ID number for uniquely identifying the page resource plug-in. Every preset time interval, the mobile application needs to determine whether there is a new version of each page resource plug-in. Based on the ID number of the page resource plug-in to be detected, the mobile application sends a plug-in update detection request carrying the ID number to the first server.

When the first server receives the plug-in update detection request, it parses out the ID number of the page resource plug-in carried in the plug-in update detection request. The first server screens out the page resource plug-in corresponding to the ID number from among the page resource plug-ins published at the current moment. According to the static cache resources called by the filtered page resource plug-in, the first server generates a first cache file list to record the resource names and MD5 values of each static cache resource in the first cache file list, and the first cache file The file list is returned to the mobile application as a response to the plug-in update detection request.

Preferably, the resource home page addresses corresponding to each ID number are stored in the first server, and when the preset time interval arrives, the first server crawls the page resources in the resource home page addresses according to the resource home page addresses stored therein, To integrate the crawling results into a new page resource plug-in, and publish the page resource plug-in. In the embodiment of the present invention, the administrator of the site does not need to manually log in to the static cache resource release platform and manually upload the updated page resource plug-in, but only needs to store the address of the resource home page of the site in the first server to realize the page resource plug-in. Automatic crawling and regular update, thus reducing the operational complexity of page resource plug-ins in the update and release process.

S106: Receive the first cache file list returned by the first server according to the plug-in update detection request, where the first cache file list includes the MD5 value of each static cache resource.

S107: Read the MD5 value of each static cache resource in the second cache file list obtained by running the page resource plug-in.

After running the locally stored page resource plug-in, a cache file list can also be obtained. In order to distinguish it from the cache file list returned by the first server, the cache file list obtained after running the locally stored page resource plug-in is called the second cache List of Documents. It can be known from the above step S103 that the second cache file list records resource names of each static cache resource in the compressed package corresponding to the page resource plug-in and the MD5 value corresponding to each static cache resource.

S108: For each static cache resource, if its MD5 value in the first cache file list is different from its MD5 value in the second cache file list, update the static cache resource, and save all The second cache file list is updated to the first cache file list.

The MD5 value corresponding to each resource name in the first cache file list is sequentially read. Wherein, when reading the MD5 value corresponding to each resource name, find out the MD5 value corresponding to the resource name in the second cache file list. If the two MD5 values are different, it is determined that a new version of the static cache resource corresponding to the resource name has been released.

In particular, if a certain resource name in the first cache file list does not exist in the second cache file list, it is also determined that a new version of the static cache resource corresponding to the resource name has been released.

When it is determined that a new version of a certain static cache resource has been released, the static cache resource is downloaded from the first server to update the locally stored static cache resource of the mobile application. Moreover, the first cache file list originally stored by the mobile application is deleted, so as to update the second cache file list to the first cache file list.

Preferably, when updating the static cache resource locally stored in the mobile application, only the incremental data of the static cache resource is downloaded from the first server, so as to reduce the amount of data to be downloaded by the mobile application, thereby improving the performance of the static cache resource. Update efficiency.

In the embodiment of the present invention, the first cache file list related to the newly released static cache resource is obtained regularly, and the MD5 value of the static cache resource in the second cache file list stored locally is determined to be consistent with the first cache file list. Whether the MD5 value of a certain static cache resource is the same can quickly detect whether a new version of the static cache resource in the mobile application has been released, which improves the detection efficiency; When the MD5 values in the file list are different, by updating the static cache resource, the download of the entire page resource plug-in with a large amount of information can be avoided, thereby improving the update efficiency of the static cache resource.

As yet another embodiment of the present invention, as shown in FIG. 3, after the above S103, further includes:

S109: Obtain a preset decryption algorithm.

S110: Using the decryption algorithm, decrypt the plurality of static cache resources stored locally under the site.

In the embodiment of the present invention, the page resource plug-in packaged into the installation package of the mobile application, the static cache resource corresponding to each page resource plug-in, and the cache file list are all encrypted file data based on AES (Advanced Encryption Standard, Advanced Encryption Standard) . When the mobile application is running and the page loading request is intercepted, a decryption algorithm acquisition event is triggered to read the decryption algorithm pre-stored in the mobile application. Through the decryption algorithm, each encrypted static cache resource is decrypted, so as to decrypt the compressed package, cache file list and various static cache resources corresponding to the page resource plug-in.

In the embodiment of the present invention, while the page resource plug-in and the application program are packaged, various data files such as the static cache resource are encrypted, so that the static cache resource can be stored in the mobile terminal in an encrypted form. Only when the mobile application is running, can the page loading request be intercepted to obtain the decryption algorithm used to decrypt the page resource plug-in. Therefore, even if the static cache resource is intercepted by other criminals, as long as the mobile application is not running, the static cache resource will not It cannot be decrypted, thus ensuring the code security of static cache resources.

As an embodiment of the present invention, as shown in FIG. 5, the above S104 specifically includes:

S1041: Obtain the static cache resource matching the page address from among the plurality of static cache resources, and calculate an MD5 value of the static cache resource.

In the embodiment of the present invention, according to the page address carried in the page loading request, the decompressed static cache resources are searched for a static cache resource matching the page address. Through the MD5 algorithm pre-stored locally, the searched static cache resource is processed to calculate the MD5 value of the static cache resource at the current moment. Wherein, the locally stored MD5 algorithm is the same as the MD5 algorithm used by the first server when distributing the page resource plug-in.

S1042: From each MD5 value pre-recorded in the second cache file list, read the MD5 value corresponding to the static cache resource.

According to the resource name of the static cache resource, search the MD5 value corresponding to the resource name in the locally stored cache file list to determine whether the MD5 value obtained by the search is the same as the MD5 value calculated in real time at the current moment.

S1043: If the read MD5 value is the same as the calculated MD5 value, in the application program, load the static cache resource according to a preset network view.

S1044: If the read MD5 value is different from the calculated MD5 value, send the page loading request to the second server, so as to load the web page resource based on the page address.

Different data contents have different MD5 values calculated by the same MD5 algorithm. Therefore, if the static cache resource stored locally changes at the current moment, or the MD5 value of the static cache resource recorded in the cache file list is the latest released MD5 value, then the MD5 value calculated by the MD5 algorithm will be the same as the cache file list The MD5 values stored in are different, so that it can be judged whether the static cache resource stored locally has been tampered with or whether it is the latest version of the page resource.

If the calculated MD5 value is the same as the MD5 value read in the second cache file list, it can be determined that the locally stored static cache resource is the latest published page resource and has not been tampered with. Therefore, through the preset WebView, Load the static cache resource directly.

If the calculated MD5 value is different from the MD5 value read in the second cache file list, it can be determined that the locally stored static cache resource is an old version of the page resource, or has been illegally tampered with. At this point, the intercepted page loading request is resent to the resource server corresponding to the page address it carries, so as to request to obtain the page resource online.

In the embodiment of the present invention, by using the MD5 algorithm to calculate the real-time MD5 value of the static cache resource, and comparing whether the MD5 value is the same as the MD5 value in the cache file list, the tamper-proof check of the static cache resource is realized; The manifest may be updated before the static cache resource file itself, so if the calculated MD5 value is different from the MD5 value in the cache file manifest, it can be preliminarily judged that the static cache resource stored locally may be different from the latest version of the static cache resource , so by loading page resources online in real time, it is ensured that the mobile application can maximize the loading speed of page resources and at the same time display the latest version of page resources, thereby improving the reliability of mobile applications.

It should be understood that the sequence numbers of the steps in the above embodiments do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation to the implementation process of the embodiment of the present invention.

Corresponding to the page resource loading method described in the above embodiments, FIG. 5 shows a structural block diagram of a page resource loading device provided by an embodiment of the present invention. For convenience of description, only parts related to the embodiment of the present invention are shown.

Referring to Figure 5, the device includes:

The intercepting unit 501 is configured to intercept a page loading request when a page loading event is triggered, and obtain a page address carried in the page loading request.

The determining unit 502 is configured to determine a page resource plug-in matching the site based on the site corresponding to the page address, and the page resource plug-in is pre-stored in the installation package of the application program.

The decompression unit 503 is configured to run the page resource plug-in to obtain a plurality of static cache resources stored locally under the site.

The loading unit 504 is configured to load, in the application program, the static cache resource matching the page address according to a preset network view.

Optionally, as shown in Figure 6, the page resource loading device further includes:

The requesting unit 505 is configured to send a plug-in update detection request to the first server every preset time interval.

The receiving unit 506 is configured to receive the first cache file list returned by the first server according to the plug-in update detection request, the first cache file list includes the MD5 value of each of the static cache resources.

The reading unit 507 is configured to read the MD5 value of each static cache resource in the second cache file list obtained by running the page resource plug-in.

An updating unit 508, configured to, for each of the static cache resources, update the static cache resource if its MD5 value in the first cache file list is different from its MD5 value in the second cache file list , and update the second cache file list to the first cache file list.

Optionally, the request unit 507 includes:

The request subunit is configured to send a plug-in update detection request to the first server every preset time interval, and the plug-in update detection request includes the identification number of the page resource plug-in, so that the first server can communicate with From the plug-in resource page bound with the identification number, the static cache resource published at the current moment is extracted, and the first server returns the first cache file list related to the static cache resource.

Optionally, as shown in Figure 7, the page resource loading device further includes:

The obtaining unit 509 is configured to obtain a preset decryption algorithm.

The decryption unit 510 is configured to use the decryption algorithm to decrypt the plurality of locally stored static cache resources under the site.

Optionally, the loading unit 504 includes:

The calculation subunit is configured to obtain the static cache resource matching the page address from among the plurality of static cache resources, and calculate the MD5 value of the static cache resource.

The acquiring subunit is configured to read the MD5 value corresponding to the static cache resource among the MD5 values pre-recorded in the second cache file list.

The loading subunit is configured to load the static cache resource in the application program according to the preset network view if the read MD5 value is the same as the calculated MD5 value.

The sending subunit is configured to send the page loading request to the second server to load the web page resource based on the page address if the read MD5 value is different from the calculated MD5 value.

In the embodiment of the present invention, by storing page resource plug-ins matching multiple sites in the application installation package of the Hybrid App, and making the Hybrid App decompress the locally stored page resource plug-ins when intercepting a page loading request, to Loading the static cache resources that match the page loading request ensures that the Hybrid App can quickly load the page resources locally even when the page resources are loaded for the first time, thereby reducing the number of requests for page resources from the remote server and greatly reducing the It reduces the time-consuming loading of page resources, thus improving the performance of the Hybrid App.

Fig. 8 is a schematic diagram of a terminal device provided by an embodiment of the present invention. As shown in FIG. 8 , the terminal device 8 of this embodiment includes: a processor 80 , a memory 81 , and a computer program 82 stored in the memory 81 and operable on the processor 80 , such as a page resource loading program. When the processor 80 executes the computer program 82, it implements the steps in the above embodiments of the page resource loading method, for example, steps 101 to 104 shown in FIG. 1 . Alternatively, when the processor 80 executes the computer program 82, functions of the modules/units in the above-mentioned device embodiments, such as the functions of the units 51 to 54 shown in FIG. 5 , are realized.

Exemplarily, the computer program 82 can be divided into one or more modules/units, and the one or more modules/units are stored in the memory 81 and executed by the processor 80 to complete this invention. The one or more modules/units may be a series of computer program instruction segments capable of accomplishing specific functions, and the instruction segments are used to describe the execution process of the computer program 82 in the terminal device 8 .

The terminal device 8 may be computing devices such as desktop computers, notebooks, palmtop computers, and cloud servers. The terminal device may include, but not limited to, a processor 80 and a memory 81 . Those skilled in the art can understand that FIG. 8 is only an example of the terminal device 8, and does not constitute a limitation to the terminal device 8. It may include more or less components than those shown in the figure, or combine certain components, or different components. , for example, the terminal device may also include an input and output device, a network access device, a bus, and the like.

The so-called processor 80 may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), Off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

The storage 81 includes at least one type of computer-readable storage medium, which may be an internal storage unit of the terminal device 8 , such as a hard disk or memory of the terminal device 8 . The memory 81 can also be an external storage device of the terminal device 8, such as a plug-in hard disk equipped on the terminal device 8, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc. Further, the memory 81 may also include both an internal storage unit of the terminal device 8 and an external storage device. The memory 81 is used to store the computer program and other programs and data required by the terminal device. The memory 81 can also be used to temporarily store data that has been output or will be output.

Those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used for illustration. In practical applications, the above-mentioned functions can be assigned to different functional units, Completion of modules means that the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment may be integrated into one processing unit, or each unit may exist separately physically, or two or more units may be integrated into one unit, and the above-mentioned integrated units may adopt hardware It can also be implemented in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the present application. For the specific working process of the units and modules in the above system, reference may be made to the corresponding process in the foregoing method embodiments, and details will not be repeated here.

In the above-mentioned embodiments, the descriptions of each embodiment have their own emphases, and for parts that are not detailed or recorded in a certain embodiment, refer to the relevant descriptions of other embodiments.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal equipment and method may be implemented in other ways. For example, the device/terminal device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units Or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated module/unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention realizes all or part of the processes in the methods of the above embodiments, and can also be completed by instructing related hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer When the program is executed by the processor, the steps in the above-mentioned various method embodiments can be realized. . Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, and a read-only memory (ROM, Read-Only Memory) , random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable Excludes electrical carrier signals and telecommunication signals.

The above-described embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still implement the foregoing embodiments Modifications to the technical solutions recorded in the examples, or equivalent replacement of some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should be included in within the protection scope of the present invention.

Claims (10)

1. A kind of 1. page resource loading method, it is characterised in that including：

   When page load events are triggered, page load request is intercepted, and obtains the page load request and is taken The page address of band；

   Based on website corresponding to the page address, it is determined that the page resource plug-in unit with the site match, the page resource Plug-in unit is pre-stored within the installation kit of application program；

   The page resource plug-in unit is run, with multiple static cache resources under the website that is locally stored；

   In the application program, according to default network view, the static cache matched with the page address is loaded Resource.
2. 2. page resource loading method as claimed in claim 1, it is characterised in that also include：

   Every default time interval, update of plug-in detection request is sent to first server；

   Receive the first server and returned the first cache file inventory is asked according to update of plug-in detection, described the One cache file inventory includes the MD5 values of each static cache resource；

   In the second cache file inventory obtained by running the page resource plug-in unit, each static cache resource is read MD5 values；

   For each static cache resource, if its MD5 value in the first cache file inventory with it described the MD5 values in two cache file inventories are different, then update the static cache resource, and the second cache file inventory is updated For the first cache file inventory.
3. 3. page resource loading method as claimed in claim 2, it is characterised in that it is described every default time interval, to First server sends update of plug-in detection request, including：

   Every default time interval, update of plug-in detection request, the update of plug-in detection request are sent to first server Include the identification number of the page resource plug-in unit, so that the first server is in the plug-in resource bound with the identification number In the page, the static cache resource issued of extraction current time, and return to the first server and provided with the static cache Related the first cache file inventory in source.
4. 4. page resource loading method as claimed in claim 1, it is characterised in that inserted in the operation page resource Part, after multiple static cache resources under the website that is locally stored, in addition to：

   Obtain default decipherment algorithm；

   By the decipherment algorithm, place is decrypted to multiple static cache resources under the website that is locally stored Reason.
5. 5. page resource loading method as claimed in claim 2, it is characterised in that it is described in the application program, according to Default network view, the static cache resource matched with the page address is loaded, including：

   In the multiple static cache resource, the static cache resource matched with the page address is obtained, and calculate The MD5 values of the static cache resource；

   In each MD5 values of the second cache file inventory are pre-recorded in, read corresponding with the static cache resource MD5 values；

   If it is identical with the MD5 values being calculated to read obtained MD5 values, in the application program, according to default network View, load the static cache resource；

   If it is different from the MD5 values being calculated to read obtained MD5 values, sending the page loading to second server please Ask, to load the Webpage resource based on the page address.
6. 6. a kind of terminal device, including memory and processor, it is stored with and can transports on the processor in the memory Capable computer program, it is characterised in that described in the computing device during computer program, realize following steps：

   When page load events are triggered, page load request is intercepted, and obtains the page load request and is taken The page address of band；

   Based on website corresponding to the page address, it is determined that the page resource plug-in unit with the site match, the page resource Plug-in unit is pre-stored within the installation kit of application program；

   The page resource plug-in unit is run, with multiple static cache resources under the website that is locally stored；

   In the application program, according to default network view, the static cache matched with the page address is loaded Resource.
7. 7. terminal device as claimed in claim 6, it is characterised in that described in the computing device during computer program, also Realize following steps：

   Every default time interval, update of plug-in detection request is sent to first server；

   Receive the first server and returned the first cache file inventory is asked according to update of plug-in detection, described the One cache file inventory includes the MD5 values of each static cache resource；

   In the second cache file inventory obtained by running the page resource plug-in unit, each static cache resource is read MD5 values；

   For each static cache resource, if its MD5 value in the first cache file inventory with it described the MD5 values in two cache file inventories are different, then update the static cache resource, and the second cache file inventory is updated For the first cache file inventory.
8. 8. terminal device as claimed in claim 7, it is characterised in that it is described every default time interval, to first service Device sends the step of update of plug-in detection request, specifically includes：

   Every default time interval, update of plug-in detection request, the update of plug-in detection request are sent to first server Include the identification number of the page resource plug-in unit, so that the first server is in the plug-in resource bound with the identification number In the page, the static cache resource issued of extraction current time, and return to the first server and provided with the static cache Related the first cache file inventory in source.
9. 9. terminal device as claimed in claim 7, it is characterised in that it is described in the application program, according to default net Network view, load matched with the page address the static cache resource the step of, specifically include：

   In the multiple static cache resource, the static cache resource matched with the page address is obtained, and calculate The MD5 values of the static cache resource；

   In each MD5 values of the second cache file inventory are pre-recorded in, read corresponding with the static cache resource MD5 values；

   If it is identical with the MD5 values being calculated to read obtained MD5 values, in the application program, according to default network View, load the static cache resource；

   If it is different from the MD5 values being calculated to read obtained MD5 values, sending the page loading to second server please Ask, to load the Webpage resource based on the page address.
10. 10. a kind of computer-readable recording medium, the computer-readable recording medium storage has computer program, and its feature exists In when the computer program is executed by processor the step of realization such as any one of claim 1 to 5 methods described.