CN113535199A - WebApp-based website updating method, system and storage medium - Google Patents
WebApp-based website updating method, system and storage medium Download PDFInfo
- Publication number
- CN113535199A CN113535199A CN202110578040.4A CN202110578040A CN113535199A CN 113535199 A CN113535199 A CN 113535199A CN 202110578040 A CN202110578040 A CN 202110578040A CN 113535199 A CN113535199 A CN 113535199A
- Authority
- CN
- China
- Prior art keywords
- version number
- file
- website
- folder
- url
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a website updating method, a website updating system and a storage medium based on WebApp, which relate to the network technology and comprise the following steps: s101, releasing a homepage file, a version number file and a static resource folder of a new version in a version number folder of a website root directory; s102, copying the content in the version number folder to the website root directory; the method comprises the following steps that a homepage file is provided with an execution code, and when the execution code is loaded by a browser, the following steps are realized: s201, acquiring a version number file under the website root directory, and analyzing the acquired version number file to obtain a latest version number; s202, judging whether the version number in the first URL accessed by the current browser is consistent with the latest version number, if not, executing S203; s203, replacing the version number in the first URL with the latest version number to obtain a second URL, and jumping to access the second URL. The method and the device can ensure that the user can access the latest homepage file.
Description
Technical Field
The application relates to a network technology, in particular to a WebApp-based website update processing method, a WebApp-based website update processing system and a storage medium.
Background
The browser requests a resource from the server for the first time, and the server returns a response header for the resource as above (Chrome). After the browser parses, the resource is cached along with the header. When the browser requests the resource again next time, the browser searches in the Cache first, and calculates whether the resource is overdue according to Expires or Cache-Control after the resource is found. If not, the cache is hit, and the cache resources are directly loaded. And if the resource packet is expired, directly loading the resource from the server, and simultaneously re-caching the new resource packet.
If the server resources are updated during the cache validity period, the browser needs to be notified to abandon the local cache. One existing solution is to add a hash fingerprint (calculated according to module contents) to an output file at a compiling stage by using Webpack, thereby implementing incremental updating of front-end static resources.
However, even if a hash fingerprint is added to the loaded resource file, such as/js/myjs- { $ hash value }. js or/js/myjs.jsv { $ hash value }, the cache update of js and css is solved, and the cache update cannot be applied to the entry index.
If the user does not strongly refresh the page (even if F5 is refreshed, different browsers differ, for example, Chrome uses cache, Edge, Firefox give up cache), the loaded html may still be cached, resulting in failure to load the latest hash fingerprint resource. A common solution to solve html caching is to set in the meta tag.
However, since the browser implementations of many manufacturers are very different, the method cannot be used in many browsers, and the cache problem still cannot be completely solved.
Disclosure of Invention
The present invention is directed to solving at least one of the problems of the prior art. Therefore, the invention provides a website updating method, a website updating system and a website updating storage medium based on WebApp, and aims to solve the problem that a homepage cannot be updated in time.
The embodiment of the application provides:
a website updating method based on WebApp comprises the following steps:
s101, releasing a homepage file, a version number file and a static resource folder of a new version in a version number folder of a website root directory, wherein the static resource folder comprises a plurality of static resources;
s102, copying the content in the version number folder to the website root directory so as to cover the homepage file, the version number file and the static resource folder of the previous version;
wherein, the homepage file of any version is configured with an execution code, and when the execution code is loaded by a browser, the following steps are implemented:
s201, acquiring a version number file under the website root directory, and analyzing the acquired version number file to obtain a latest version number;
s202, judging whether the version number in the first URL accessed by the current browser is consistent with the latest version number, if not, executing S203;
s203, replacing the version number in the first URL with the latest version number to obtain a second URL, and jumping to access the second URL.
In some embodiments, in S202, if the version number in the first URL accessed by the current browser is consistent with the latest version number, the static resource file is loaded according to the hash fingerprint in the homepage file loaded by the current browser;
and when the static resource file is loaded, the static resource file is loaded from a local cache static resource folder preferentially.
In some embodiments, after S203, further comprising:
and S204, caching the homepage file under the website directory corresponding to the second URL.
In some embodiments, after S204, further comprising:
s205, caching the static resource files in the static resource folder in the website directory corresponding to the second URL according to the hash fingerprints in the homepage file cached in the step 204.
In some embodiments, before S101, the following steps are further included:
s1001, acquiring and executing an issuing instruction;
s1002, judging whether a website root directory exists or not, if so, executing S1003, otherwise, creating a website root directory and a version number folder specified by the release instruction, and executing S101;
s1003, judging whether a version number folder specified in the issuing instruction exists, if so, executing S101, otherwise, creating the version number folder specified in the issuing instruction under the website root directory, and executing S101.
In some embodiments, the homepage file is an html file, and the version number file is a JS file.
In some embodiments, the cache of the static resource file corresponding to each version number is shared during the lifecycle.
On the other hand, the embodiment discloses a website updating system based on WebApp, which includes:
a publishing module to perform: s101, releasing a homepage file, a version number file and a static resource folder of a new version in a version number folder of a website root directory, wherein the static resource folder comprises a plurality of static resources;
a copy module to perform: s102, copying the content in the release version number folder to the website root directory so as to cover the previous version of the homepage file, the version number file and the static resource folder;
wherein, the homepage file of any version is configured with an execution code, and when the execution code is loaded by a browser, the following steps are implemented:
s201, acquiring a version number file under the website root directory, and analyzing the acquired version number file to obtain a latest version number;
s202, judging whether the version number in the first URL accessed by the current browser is consistent with the latest version number, if not, executing S203;
s203, replacing the version number in the first URL with the latest version number to obtain a second URL, and jumping to access the second URL.
On the other hand, the embodiment discloses a website updating system based on WebApp, which includes:
a memory for storing a program;
and the processor is used for loading the memory to execute the WebApp-based website updating method.
On the other hand, the embodiment discloses a storage medium, which stores a program, and when the program is loaded by a processor, the website updating method based on the WebApp is realized.
According to the scheme of the embodiment of the application, when the website of the WebApp releases the new version, the homepage file, the version number file and the static resource folder of the new version are released in the root directory, the contents are covered in the root directory, the execution code is configured in the homepage file, when the execution code is executed, the version number file is obtained from the root directory of the website, the latest version number is obtained, whether access skip needs to be carried out or not is judged based on whether the version number is the same as that of the first URL or not, and through the mode, no matter the new version is released at any time, a user can access the latest homepage file and load the latest version number file into the correct static resource file, so that the page displayed by the WebApp can be guaranteed to be the latest page.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a website updating method based on WebApp according to an embodiment of the present invention;
fig. 2 is a flowchart of a function implemented by executing a code in a website updating method based on WebApp according to an embodiment of the present invention;
FIG. 3 is a diagram of a root directory provided by an embodiment of the invention;
fig. 4 is a schematic diagram of a version number directory provided by an embodiment of the present invention;
fig. 5 is a flowchart of folder creation provided by an embodiment of the present invention.
Detailed Description
In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below through embodiments with reference to the accompanying drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present invention, the meaning of a plurality is one or more, the meaning of a plurality is two or more, and the above, below, exceeding, etc. are understood as excluding the present numbers, and the above, below, within, etc. are understood as including the present numbers. If the first and second are described for the purpose of distinguishing technical features, they are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated or implicitly indicating the precedence of the technical features indicated.
In the description of the present invention, unless otherwise explicitly defined, terms such as set, etc. should be broadly construed, and those skilled in the art can reasonably determine the specific meanings of the above terms in the present invention in combination with the detailed contents of the technical solutions.
In the description of the present invention, reference to the description of the terms "one embodiment," "some embodiments," "an illustrative embodiment," "an example," "a specific example," or "some examples," etc., means that a particular feature or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Part of software functions are realized based on WebApp, and if a user accesses an overdue version in a cache, operation errors of the user can be caused, and the functions cannot be completed.
To this end, referring to fig. 1 and fig. 2, the present embodiment discloses a website updating method based on WebApp, including the following steps:
s101, releasing a homepage file, a version number file and a static resource folder of a new version in a version number folder of a website root directory, wherein the static resource folder comprises a plurality of static resources.
Referring to fig. 3, the directory/root/file includes a version number folder of version V1, a version number folder of version V2, static resource folder static, homepage file index, version number file version, and description document readme. As shown in fig. 4, in this step, taking the release version V2 as an example, the content released under the folder V2 includes a static resource folder static, a home page file index, a version number file version, and a description document readme corresponding to the version V2.
S102, copying the content in the version number folder to the website root directory so as to cover the previous version of the homepage file, the version number file and the static resource folder.
The file shown in fig. 4 is copied to the root directory/root/because the names of several files corresponding to each version are the same, if there is a file corresponding to one version in the root directory itself before copying, the new version of the file will overwrite the contents in this step.
That means, as the version is released, the files in the root directory will be updated to the files corresponding to the new version, and all the folders corresponding to the old version will exist in the root directory (assuming that the folders of the old version are not deleted).
Wherein, the homepage file of any version is configured with an execution code, and when the execution code is loaded by a browser, the following steps are implemented:
s201, obtaining a version number file under the website root directory, and analyzing the obtained version number file to obtain a latest version number.
In this embodiment, all versions of the homepage file are configured with an execution code, and the execution code is used to access the root directory and obtain the version file under the root directory, so that no matter which version of the homepage is cached, the browser is not prevented from obtaining the latest version number. In this embodiment, the version number file is a JaveScript file. And the homepage file is an html file. With regard to the implementation of the execution code, the access address of the root directory may be written in the execution code. For example, the website is www.abc.com, the user accesses www.abc.com/V1, and if the current latest version is V2, the executing code will access www.abc.com first, which is equivalent to accessing the root directory, and then obtain the version number file from the root directory, and obtain the current latest version as V2.
S202, judging whether the version number in the first URL accessed by the current browser is consistent with the latest version number, if not, executing S203.
S203, replacing the version number in the first URL with the latest version number to obtain a second URL, and jumping to access the second URL.
The latest version number obtained from the above step S201 can be compared with the version number of www.abc.com/V1 in the access address, i.e. V1, and if not, the V1 in the URL is replaced by V2 to obtain a second URL, i.e. www.abc.com/V2. Then the second URL is accessed, which ensures that the latest home page is accessed by the browser each time.
It will be appreciated that if the current user accesses for the first time, the address of the access is www.abc.com, it can also get the latest home page and latest version number under the root directory and can set jump access. If the current user does not access for the first time, he has cached the V1 version locally, and also gets the latest version number, for example V2, and performs the jump. Therefore, the method is compatible with the caching mode of the current browser, the browser does not need to be modified greatly, and only the file is released and the execution code is added in the homepage file according to the method.
Through the above embodiment, when the new version is released at the website of the WebApp, the home page file, the version number file and the static resource folder of the new version are released in the root directory, the contents are covered in the root directory, the execution code is configured in the home page file, when the execution code is executed, the version number file is obtained from the root directory of the website, the latest version number is obtained, whether access skip needs to be carried out or not is judged based on whether the version number is the same as that of the first URL, and through the above mode, no matter the new version is released at any time, a user can access the latest home page file and load the latest home page file into a correct static resource file, so that the page displayed by the WebApp can be ensured to be the latest page. The method is compatible with the existing cache mechanism, ensures that the user accesses a normal homepage under the condition that the user does not forcibly refresh, avoids errors in user operation, and optimizes user experience.
In some embodiments, in S202, if the version number in the first URL accessed by the current browser is consistent with the latest version number, the static resource file is loaded according to the hash fingerprint in the homepage file loaded by the current browser;
and when the static resource file is loaded, the static resource file is loaded from a local cache static resource folder preferentially.
In this embodiment, if the current version number is the latest, it means that the static resource file cached last time, which is also a valid file in general, can be obtained from the local cache. This approach is compatible with current caching mechanisms. Network traffic may be reduced.
Referring to fig. 2, in some embodiments, after S203, further comprising:
and S204, caching the homepage file under the website directory corresponding to the second URL.
In this embodiment, since the second URL is the first access, the homepage file under the second URL may be cached. The next time the second URL is accessed, the cache may be used directly.
Referring to fig. 2, in some embodiments, after S204, further comprising:
s205, caching the static resource files in the static resource folder in the website directory corresponding to the second URL according to the hash fingerprints in the homepage file cached in the step 204.
Similarly, in this step, when the homepage file corresponding to the second URL is loaded, the static resource file in the static resource folder is cached according to the hash fingerprint in the cached homepage file, so that network transmission is reduced in the next access. The hash fingerprint is a hash code calculated by a hash algorithm according to the static resource file, and is referred to as a hash fingerprint.
Referring to fig. 5, in some embodiments, before S101, the following steps are further included:
s1001, obtaining and executing an issuing instruction.
And S1002, judging whether a website root directory exists or not, if so, executing S1003, otherwise, creating the website root directory and a version number folder specified by the release instruction, and executing S101.
S1003, judging whether a version number folder specified in the issuing instruction exists, if so, executing S101, otherwise, creating the version number folder specified in the issuing instruction under the website root directory, and executing S101.
Before the method is executed, the method also comprises a folder creation step, wherein the creation logic is that if the root directory does not exist, the root directory is indicated to be released for the first time, the root directory is created first, and then the folder with the version number corresponding to the current version is created. If a following directory exists, the description is not first published or the root directory has been artificially created. At this time, a currently issued version number folder is created under the root directory as appropriate.
In some embodiments, the homepage file is an html file, and the version number file is a JS file.
In some embodiments, the cache of the static resource file corresponding to each version number is shared during the lifecycle.
In this embodiment, the cache of the static resource file can be shared by the homepage files with different version numbers during the validity period, and there may be a small amount of changes between different version numbers, so that a part of the static resource can be reused. Therefore, the transmission of the network can be reduced, and the network bandwidth can be saved.
The embodiment discloses a website updating system based on WebApp, which comprises:
a publishing module to perform: s101, releasing a homepage file, a version number file and a static resource folder of a new version in a version number folder of a website root directory, wherein the static resource folder comprises a plurality of static resources;
a copy module to perform: s102, copying the content in the release version number folder to the website root directory so as to cover the previous version of the homepage file, the version number file and the static resource folder;
wherein, the homepage file of any version is configured with an execution code, and when the execution code is loaded by a browser, the following steps are implemented:
s201, acquiring a version number file under the website root directory, and analyzing the acquired version number file to obtain a latest version number;
s202, judging whether the version number in the first URL accessed by the current browser is consistent with the latest version number, if not, executing S203;
s203, replacing the version number in the first URL with the latest version number to obtain a second URL, and jumping to access the second URL.
The embodiment discloses a website updating system based on WebApp, which comprises:
a memory for storing a program;
and the processor is used for loading the memory to execute the WebApp-based website updating method.
The embodiment discloses a storage medium, which stores a program, and when the program is loaded by a processor, the WebApp-based website updating method is realized.
The above-described hardware embodiment may also achieve the same technical effects as the method embodiment.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims (10)
1. A website updating method based on WebApp is characterized by comprising the following steps:
s101, releasing a homepage file, a version number file and a static resource folder of a new version in a version number folder of a website root directory, wherein the static resource folder comprises a plurality of static resources;
s102, copying the content in the version number folder to the website root directory so as to cover the homepage file, the version number file and the static resource folder of the previous version;
wherein, the homepage file of any version is configured with an execution code, and when the execution code is loaded by a browser, the following steps are implemented:
s201, acquiring a version number file under the website root directory, and analyzing the acquired version number file to obtain a latest version number;
s202, judging whether the version number in the first URL accessed by the current browser is consistent with the latest version number, if not, executing S203;
s203, replacing the version number in the first URL with the latest version number to obtain a second URL, and jumping to access the second URL.
2. The WebApp-based website updating method according to claim 1, wherein in S202, if a version number in a first URL accessed by a current browser is consistent with the latest version number, a static resource file is loaded according to a hash fingerprint in a homepage file loaded by the current browser;
and when the static resource file is loaded, the static resource file is loaded from a local cache static resource folder preferentially.
3. The WebApp-based website updating method according to claim 1, further comprising after S203:
and S204, caching the homepage file under the website directory corresponding to the second URL.
4. The WebApp-based website updating method according to claim 3, further comprising after S204:
s205, caching the static resource files in the static resource folder in the website directory corresponding to the second URL according to the hash fingerprints in the homepage file cached in the step 204.
5. The WebApp-based website updating method according to claim 4, further comprising the following steps before S101:
s1001, acquiring and executing an issuing instruction;
s1002, judging whether a website root directory exists or not, if so, executing S1003, otherwise, creating a website root directory and a version number folder specified by the release instruction, and executing S101;
s1003, judging whether a version number folder specified in the issuing instruction exists, if so, executing S101, otherwise, creating the version number folder specified in the issuing instruction under the website root directory, and executing S101.
6. The WebApp-based website updating method of claim 1, wherein the homepage file is an html file, and the version number file is a JS file.
7. The WebApp-based website updating method of claim 1, wherein the cache of the static resource file corresponding to each version number is shared in a lifecycle.
8. A website updating system based on WebApp is characterized by comprising:
a publishing module to perform: s101, releasing a homepage file, a version number file and a static resource folder of a new version in a version number folder of a website root directory, wherein the static resource folder comprises a plurality of static resources;
a copy module to perform: s102, copying the content in the release version number folder to the website root directory so as to cover the previous version of the homepage file, the version number file and the static resource folder;
wherein, the homepage file of any version is configured with an execution code, and when the execution code is loaded by a browser, the following steps are implemented:
s201, acquiring a version number file under the website root directory, and analyzing the acquired version number file to obtain a latest version number;
s202, judging whether the version number in the first URL accessed by the current browser is consistent with the latest version number, if not, executing S203;
s203, replacing the version number in the first URL with the latest version number to obtain a second URL, and jumping to access the second URL.
9. A website updating system based on WebApp is characterized by comprising:
a memory for storing a program;
a processor for loading the memory to perform the WebApp-based website updating method of any one of claims 1-7.
10. A storage medium storing a program which, when loaded by a processor, implements the WebApp-based website updating method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110578040.4A CN113535199A (en) | 2021-05-26 | 2021-05-26 | WebApp-based website updating method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110578040.4A CN113535199A (en) | 2021-05-26 | 2021-05-26 | WebApp-based website updating method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113535199A true CN113535199A (en) | 2021-10-22 |
Family
ID=78124446
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110578040.4A Pending CN113535199A (en) | 2021-05-26 | 2021-05-26 | WebApp-based website updating method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535199A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114924740A (en) * | 2022-04-26 | 2022-08-19 | 江苏康众汽配有限公司 | Active detection method for resource failure in front-end single-page application |
-
2021
- 2021-05-26 CN CN202110578040.4A patent/CN113535199A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114924740A (en) * | 2022-04-26 | 2022-08-19 | 江苏康众汽配有限公司 | Active detection method for resource failure in front-end single-page application |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2673403C2 (en) | Website access method, device and website system | |
| CN108287839B (en) | Page loading method and equipment | |
| US9077681B2 (en) | Page loading optimization using page-maintained cache | |
| CN109388766B (en) | Page loading method and device | |
| US10291738B1 (en) | Speculative prefetch of resources across page loads | |
| US9531829B1 (en) | Smart hierarchical cache using HTML5 storage APIs | |
| US20090031212A1 (en) | Embedded system with web-based user interface, firmware structure thereof and method for providing information thereof | |
| CN108536617B (en) | Cache management method, medium, system and electronic device | |
| CN111666497A (en) | Application program loading method and device, electronic equipment and readable storage medium | |
| CN102937981A (en) | Webpage representing system and method | |
| US9503541B2 (en) | Fast mobile web applications using cloud caching | |
| CN112486552A (en) | Server hot update method, device, equipment and storage medium | |
| CN103530420A (en) | Data file dynamic update method and device | |
| CN103647811A (en) | A method and an apparatus for application's accessing backstage service | |
| CN113535199A (en) | WebApp-based website updating method, system and storage medium | |
| CN117061615B (en) | Cache path acquisition method, device, computer equipment and storage medium | |
| US9317432B2 (en) | Methods and systems for consistently replicating data | |
| CN112395437B (en) | 3D model loading method and device, electronic equipment and storage medium | |
| US7162717B1 (en) | Compressed file patcher | |
| CN105242960B (en) | Method for processing system function call request and browser | |
| CN103258055A (en) | Device and method for file downloading | |
| US8793663B2 (en) | Smart cache for a server test environment in an application development tool | |
| CN111753233B (en) | Third-party H5 page loading method and device and computer readable storage medium | |
| CN111078257B (en) | H5 application package loading method and related device | |
| CN113760390A (en) | Page file loading method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |