CN115509546A - Front-end deployment method and device, electronic equipment and storage medium - Google Patents

Front-end deployment method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN115509546A
CN115509546A CN202211207797.3A CN202211207797A CN115509546A CN 115509546 A CN115509546 A CN 115509546A CN 202211207797 A CN202211207797 A CN 202211207797A CN 115509546 A CN115509546 A CN 115509546A
Authority
CN
China
Prior art keywords
html
static
file
redis
acquiring
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
Application number
CN202211207797.3A
Other languages
Chinese (zh)
Inventor
陈振华
李晓捷
朱辰昊
黄子龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zaihui Shanghai Network Technology Co ltd
Original Assignee
Zaihui Shanghai Network Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zaihui Shanghai Network Technology Co ltd filed Critical Zaihui Shanghai Network Technology Co ltd
Priority to CN202211207797.3A priority Critical patent/CN115509546A/en
Publication of CN115509546A publication Critical patent/CN115509546A/en
Pending legal-status Critical Current

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
    • 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/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
    • 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/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
    • 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)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention relates to a front-end deployment method, a front-end deployment device, electronic equipment and a storage medium. The method for front-end deployment comprises the following steps: s1, constructing a CLI tool, wherein the CLI tool is used for tools, packaging and deploying front-end pages and related static resources, and provides a deployment scheme which can be used for switching millisecond-level web page versions; and S2, constructing a server transparent proxy Samaritan, wherein the Samaritan is used for displaying relevant webpages needed by the client to the user. The front-end deployment method can quickly and flexibly realize front-end deployment.

Description

Front-end deployment method and device, electronic equipment and storage medium
Technical Field
The invention relates to the technical field of internet, in particular to a front-end deployment method, a front-end deployment device, electronic equipment and a storage medium.
Background
Front end: the foreground part of the website runs on browsers such as a PC (personal computer) end and a mobile end and displays the webpages browsed by the user. A rear end: what users cannot see is usually data interaction and website data storage and reading with front-end engineers, relatively speaking, the back-end relates to more logic codes than the front-end, and the back-end considers the implementation of underlying business logic, the stability and performance of the platform, and the like. Front-end and back-end generally refer to differences in code.
At present, in the field of front-end development, how to deploy a front-end webpage does not always have a unified solution. Most deployments adopt a manual uploading mode, and are complex to operate and inconvenient to maintain. It is slow and inflexible.
Therefore, with the development of internet technology, there is a need to develop a fast and flexible front-end deployment solution.
Disclosure of Invention
The invention aims to solve the technical problems of low speed and inflexibility when a front-end webpage is deployed.
To solve the above technical problem, according to an aspect of the present invention, there is provided a front-end deployment method, including: s1, constructing a CLI (command-line interface) tool, wherein the CLI tool is used for tools, packaging and deploying front-end pages and related static resources, and provides a deployment scheme which can switch the version of the web page at millisecond level; and S2, constructing a server transparent proxy Samaritan, wherein the Samaritan is used for displaying relevant webpages needed by the client to the user.
According to an embodiment of the present invention, step S1 may further include the steps of: s11, constructing a front-end code, and generating a static file related to a web project webpage, wherein the static file comprises: static resources of HTML, JS, CSS and pictures; s12, uploading the static files to a remote static file storage service; s13, acquiring an entry file path, taking an HTML file as an entry file, acquiring all static resources required by a webpage through the HTML file, and acquiring an HTML access link returned by a static file storage service; s14, writing the entry file path and the key of the web project into Redis (Remote directory Server, a memory cache database), and writing the HTML access link returned by the static file storage service into Redis for caching.
According to the embodiment of the present invention, in step S12, the file generated by the construction may be uploaded to a remote static file storage service, and the static file storage service keeps the file directory and the file path consistent with the position at the time of construction.
According to an embodiment of the present invention, in step S12, the static file storage service may adopt a third-party service, where the third-party service includes: OSS from Alicloun or S3 from Amazon.
According to an embodiment of the invention, in step S14, the Redis may also cache the HTML access links of the history versions for fast rollback to any one of the history versions.
According to an embodiment of the present invention, step S2 may further include the steps of: s21, acquiring a unique entrance identifier according to the website page path; s22, acquiring a corresponding HTML link in Redis through the unique entrance identifier, wherein the HTML link is requested for the first time, the HTML content is cached, and the HTML content is returned to the client; and directly returning the content of the Redis cache without first request, thereby realizing rapid front-end deployment.
According to a second aspect of the present invention, there is provided a front-end deployed apparatus comprising: the CLI tool module is used for tools, packaging and deploying front-end pages and related static resources, and provides a deployment scheme which can switch the webpage versions in millisecond level; the server side transparent proxy Samarian module is used for displaying relevant webpages needed by the client to the user.
According to the embodiment of the invention, the CLI tool module can realize the tool, pack and deploy the front-end page and the related static resources by the following steps: constructing a front-end code, and generating a static file related to a web project webpage, wherein the static file comprises: static resources of HTML, JS, CSS and pictures; uploading the static files to a remote static file storage service; acquiring an entry file path, taking an HTML file as an entry file, acquiring all static resources required by a webpage through the HTML file, and acquiring an HTML access link returned by a static file storage service; and writing the entry file path and the key of the web project into Redis, writing an HTML access link returned by the static file storage service into the Redis for caching, and simultaneously caching the HTML access link of the historical version by the Redis for quickly returning to any historical version.
According to the embodiment of the invention, the server side transparent proxy Samarian module can realize page display through the following steps: acquiring a unique entrance identifier according to a website page path; acquiring a corresponding HTML link in Redis through the unique entry identifier, wherein the HTML link is requested for the first time, the HTML content is cached, and the HTML content is returned to the client; and directly returning the content of the Redis cache without the first request, thereby realizing the rapid front-end deployment.
According to a third aspect of the present invention, there is provided an electronic apparatus comprising: a memory, a processor, and a front-end deployment program stored on the memory and executable on the processor, the front-end deployment program when executed by the processor implementing the steps of the front-end deployment method described above.
According to a fourth aspect of the present invention, a computer storage medium is provided, wherein a front-end deployment program is stored on the computer storage medium, and when executed by a processor, the front-end deployment program implements the steps of the front-end deployment method described above.
Compared with the prior art, the technical scheme provided by the embodiment of the invention can at least realize the following beneficial effects:
the front-end deployment method can realize the quick switching of the front-end page version. The entry file of the front-end page corresponding to the current web page is recorded through Redis, and the entry file comprises all information required by initialization of one web project, so that the version corresponding to the web page can be changed under the condition that only the path of the entry file in Redis is changed, and rapid deployment of the front end is realized. The time required by deployment can be saved, and the millisecond-level switching of the front-end application version can be realized. Most of the web projects upload the constructed web files to the server, and the server directly returns the files to the user. Each time of construction and deployment is troublesome, and the version switching layer takes much time. By the technical scheme of the invention, rapid deployment and rapid version switching can be realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings of the embodiments will be briefly described below, and it is apparent that the drawings in the following description only relate to some embodiments of the present invention and are not limiting on the present invention.
Fig. 1 is a flow chart illustrating a method of front-end deployment in accordance with an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the drawings of the embodiments of the present invention. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the described embodiments of the invention without inventive step, are within the scope of protection of the invention.
Unless defined otherwise, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this invention belongs. The use of "first," "second," and similar terms in the description and claims of the present application do not denote any order, quantity, or importance, but rather the terms are used to distinguish one element from another. Also, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one.
Fig. 1 is a flow chart illustrating a method of front-end deployment in accordance with an embodiment of the present invention.
As shown in fig. 1, the method of front-end deployment includes the following steps:
s1, constructing a CLI tool, wherein the CLI tool is used for tools, packaging and deploying front-end pages and related static resources, and the CLI tool provides a deployment scheme and can be used for switching webpage versions at millisecond level.
And S2, constructing a server transparent proxy Samaritan, wherein the Samaritan is used for displaying relevant webpages needed by the client to the user.
According to one or some embodiments of the invention, step S1 further comprises the steps of:
s11, constructing a front end code, and generating a static file related to a web project webpage, wherein the static file comprises: HTML, JS, CSS, static resources of pictures.
And S12, uploading the static file to a remote static file storage service.
And S13, acquiring an entry file path, taking the HTML file as an entry file, acquiring all static resources required by the webpage through the HTML file, and acquiring an HTML access link returned by the static file storage service.
S14, writing the entry file path and the key of the web project into Redis, and writing the HTML access link returned by the static file storage service into the Redis for caching.
According to one or some embodiments of the invention, in step S12, the file generated by the construction is uploaded to a remote static file storage service, and the static file storage service keeps the file directory and the file path consistent with the position at the time of construction. In step S12, the static file storage service uses a third-party service, and the third-party service includes: OSS of arrhizus or S3 of Amazon.
According to one or some embodiments of the invention, redis also caches historical version HTML access links for fast rollback to any one of the historical versions in step S14.
According to one or some embodiments of the invention, step S2 further comprises the steps of:
and S21, acquiring a unique entrance identifier according to the website page path.
S22, acquiring a corresponding HTML link in Redis through the unique entrance identifier.
The method comprises the steps of requesting for the first time, reading HTML links, caching HTML contents, and returning the HTML contents to a client; and directly returning the content of the Redis cache without first request, thereby realizing rapid front-end deployment.
The method of the scheme can realize the quick switching of the front-end page version. The entry file of the front-end page corresponding to the current web page is recorded through the Redis, and the entry file comprises all information required by web project initialization, so that the version corresponding to the web page can be changed under the condition that only the path of the entry file in the Redis is changed, and the quick deployment of the front end is realized.
When the method is used, after the Web project can release the version submission codes, the construction and deployment process is triggered. The CLI tool will compile, package the project file, expose the corresponding entry file, and name it in a special way, such as: ci.2342355. Html, the name corresponding to the current build version of the current web project. The CLI tool uploads all the constructed files to a remote static file storage service, and records an entry file: ci.2342355. Html. When we deploy the item, we will write the access address of ci.2342355. Html into the value corresponding to the key of the item in Redis.
When a user accesses a certain web project, the user firstly goes to a cache of the service to search for the entry file according to the key in the web project, and if the entry file does not exist, the user goes back to the corresponding Redis to search for the entry file.
In addition, if an online problem is encountered, any version of the history may be selected for rollback.
According to the technical scheme, the time required by deployment can be saved, and the millisecond-level switching of the front-end application version can be realized. At present, most web projects upload constructed web files to a server, and the server directly returns the files to users; each time of construction and deployment is troublesome, and the version switching layer also consumes much time. By the technical scheme of the invention, rapid deployment and rapid version switching can be realized.
According to a second aspect of the present invention, there is provided a front-end deployed apparatus comprising: the CLI tool module is used for tools, packaging and deploying front-end pages and related static resources, and provides a deployment scheme which can switch the webpage versions in millisecond level; the server side transparent proxy Samarian module is used for displaying relevant webpages needed by the client to the user.
According to one or some embodiments of the invention, the CLI tool module implements the tool, packages and deploys the front-end pages and related static resources by: constructing a front-end code, and generating a static file related to a web project webpage, wherein the static file comprises: static resources of HTML, JS, CSS and pictures; uploading the static files to a remote static file storage service; acquiring an entry file path, acquiring all static resources required by a webpage by using an HTML file as an entry file and acquiring an HTML access link returned by a static file storage service; and writing the entry file path and the key of the web project into Redis, writing an HTML access link returned by the static file storage service into the Redis for caching, and simultaneously caching the HTML access link of the historical version by the Redis for quickly returning to any historical version.
According to one or some embodiments of the invention, the server side transparent proxy Samarian module realizes page display by the following steps: acquiring a unique entrance identifier according to a website page path; acquiring a corresponding HTML link in Redis through the unique entry identifier, wherein the HTML link is requested for the first time, the HTML content is cached, and the HTML content is returned to the client; and directly returning the content of the Redis cache without first request, thereby realizing rapid front-end deployment.
According to a third aspect of the present invention, there is provided an electronic apparatus comprising: the computer-readable medium may include a memory, a processor, and a front-end deployment program stored on the memory and executable on the processor, the front-end deployment program implementing the steps of the front-end deployment method described above when executed by the processor.
According to a fourth aspect of the present invention, a computer storage medium is provided, wherein a front-end deployment program is stored on the computer storage medium, and when executed by a processor, the front-end deployment program implements the steps of the front-end deployment method described above.
According to yet another aspect of the present invention, there is provided a front-end deployed apparatus comprising: the computer-readable medium may include a memory, a processor, and a front-end deployment program stored on the memory and executable on the processor, the front-end deployment program implementing the steps of the front-end deployment method described above when executed by the processor.
There is also provided a computer storage medium according to the present invention.
The computer storage medium has stored thereon a front-end deployment program that, when executed by the processor, performs the steps of the front-end deployment method described above.
The method implemented when the front-end deployment program running on the processor is executed may refer to various embodiments of the front-end deployment method of the present invention, and details are not described here.
The invention also provides a computer program product.
The computer program product of the invention comprises a front-end deployment program which, when executed by a processor, implements the steps of the front-end deployment method as described above.
The method implemented when the front-end deployment program running on the processor is executed may refer to various embodiments of the front-end deployment method of the present invention, and details are not described here.
Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is intended to be illustrative of the present invention and not to limit the scope of the invention, which is defined by the claims appended hereto.

Claims (11)

1. A method of front-end deployment, comprising the steps of:
s1, constructing a CLI tool, wherein the CLI tool is used for tools, packaging and deploying front-end pages and related static resources, and provides a deployment scheme which can be used for switching webpage versions at millisecond level;
and S2, constructing a server transparent proxy Samaritan, wherein the Samaritan is used for displaying relevant webpages needed by the client to the user.
2. The method of claim 1, wherein the step S1 further comprises the steps of:
s11, constructing a front end code, and generating a static file related to a web project webpage, wherein the static file comprises: static resources of HTML, JS, CSS and pictures;
s12, uploading the static file to a remote static file storage service;
s13, acquiring an entry file path, taking an HTML file as an entry file, acquiring all static resources required by a webpage through the HTML file, and acquiring an HTML access link returned by a static file storage service;
and S14, writing the entry file path and the key of the web project into Redis, and writing the HTML access link returned by the static file storage service into the Redis for caching.
3. The method according to claim 2, wherein in step S12, the files generated by the construction are uploaded to a remote static file storage service, and the static file storage service keeps file directories and file paths consistent with the positions at the time of construction.
4. The method according to claim 2, wherein in step S12, the static file storage service adopts a third party service, and the third party service includes: OSS of arrhizus or S3 of Amazon.
5. The method of claim 2, wherein Redis also caches historical version HTML access links for fast rollback to any one of the historical versions in step S14.
6. The method of claim 2, wherein the step S2 further comprises the steps of:
s21, acquiring a unique entrance identifier according to the website page path;
s22, acquiring a corresponding HTML link in Redis through the unique entrance identifier,
the method comprises the steps of requesting for the first time, reading HTML links, caching HTML contents, and returning the HTML contents to a client; and directly returning the content of the Redis cache without first request, thereby realizing rapid front-end deployment.
7. A front-end deployed apparatus, comprising:
the CLI tool module is used for tools, packaging and deploying front-end pages and related static resources, and provides a deployment scheme which can switch the version of the web page at millisecond level;
the client comprises a server side transparent proxy Samarian module, wherein the server side transparent proxy Samarian module is used for displaying relevant webpages needed by a client to a user.
8. The apparatus of claim 7 wherein said CLI tool module implements tools, packages and deploys front-end pages and related static resources by:
building front-end codes and generating static files related to web project web pages, wherein the static files comprise: static resources of HTML, JS, CSS and pictures;
uploading the static file to a remote static file storage service;
acquiring an entry file path, taking an HTML file as an entry file, acquiring all static resources required by a webpage through the HTML file, and acquiring an HTML access link returned by a static file storage service;
and writing the entry file path and the key of the web item into Redis, writing an HTML access link returned by the static file storage service into Redis for caching, and simultaneously caching the HTML access link of the historical version by the Redis for quickly backing to any historical version.
9. The apparatus of claim 7, wherein the server side transparent proxy Samaritan module implements page exposure by:
acquiring a unique entrance identifier according to a website page path;
acquiring a corresponding HTML link in Redis through the unique entrance identifier,
the method comprises the steps of requesting for the first time, reading HTML links, caching HTML contents, and returning the HTML contents to a client; and directly returning the content of the Redis cache without first request, thereby realizing rapid front-end deployment.
10. An electronic device, comprising: a memory, a processor, and a front-end deployment program stored on the memory and executable on the processor, the front-end deployment program when executed by the processor implementing the steps of the front-end deployment method as claimed in any one of claims 1 to 6.
11. A computer storage medium having stored thereon a front-end deployment program that, when executed by a processor, performs the steps of the front-end deployment method of any of claims 1 to 6.
CN202211207797.3A 2022-09-30 2022-09-30 Front-end deployment method and device, electronic equipment and storage medium Pending CN115509546A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211207797.3A CN115509546A (en) 2022-09-30 2022-09-30 Front-end deployment method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211207797.3A CN115509546A (en) 2022-09-30 2022-09-30 Front-end deployment method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN115509546A true CN115509546A (en) 2022-12-23

Family

ID=84508712

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211207797.3A Pending CN115509546A (en) 2022-09-30 2022-09-30 Front-end deployment method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115509546A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270202A1 (en) * 2017-03-17 2018-09-20 Verizon Patent And Licensing Inc. Dynamic firewall configuration based on proxy container deployment
CN109284472A (en) * 2018-11-15 2019-01-29 福建省华渔教育科技有限公司 Front end webpage loading method, storage medium based on webpack
CN111970359A (en) * 2020-08-14 2020-11-20 工银科技有限公司 Front-end non-service architecture system based on node
CN113468456A (en) * 2021-07-12 2021-10-01 工银科技有限公司 Webpage rendering method and device, electronic equipment and computer-readable storage medium
CN114968198A (en) * 2022-06-16 2022-08-30 徐工汉云技术股份有限公司 Website development method, system and storage medium thereof

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270202A1 (en) * 2017-03-17 2018-09-20 Verizon Patent And Licensing Inc. Dynamic firewall configuration based on proxy container deployment
CN109284472A (en) * 2018-11-15 2019-01-29 福建省华渔教育科技有限公司 Front end webpage loading method, storage medium based on webpack
CN111970359A (en) * 2020-08-14 2020-11-20 工银科技有限公司 Front-end non-service architecture system based on node
CN113468456A (en) * 2021-07-12 2021-10-01 工银科技有限公司 Webpage rendering method and device, electronic equipment and computer-readable storage medium
CN114968198A (en) * 2022-06-16 2022-08-30 徐工汉云技术股份有限公司 Website development method, system and storage medium thereof

Similar Documents

Publication Publication Date Title
US10015226B2 (en) Methods for making AJAX web applications bookmarkable and crawlable and devices thereof
US11403262B2 (en) Local networked storage linked to remote networked storage system
US8572033B2 (en) Computing environment configuration
KR100745431B1 (en) Offline browsing with mobile device
KR102015673B1 (en) Recovery of tenant data across tenant moves
US20080147671A1 (en) System for Running Web Applications Offline and Providing Access to Native Services
AU2014252699A1 (en) Methods, systems, apparatus, products, articles and data structures for cross-platform digital content
CN102508710A (en) Method and system for switching between IE6 kernel and novel IE kernel
CN104704468A (en) Cross system installation of WEB applications
CN112612982A (en) Webpage preloading method and device and computer equipment
US20070288591A1 (en) Method, system, and program product for caching application data in a browser cache
KR100438698B1 (en) Method for executing Java Application Midlet using Communication among Java Applications
CN117390326A (en) Page management method, device, equipment and storage medium
CN112214250A (en) Application program assembly loading method and device
CN113449216A (en) File processing method and device and storage medium
CN115509546A (en) Front-end deployment method and device, electronic equipment and storage medium
CN101290584A (en) Migrating software use mode based on system call wrapping technology
CN114528510A (en) Webpage data processing method and device, electronic equipment and medium
CN113961298A (en) Page switching method, device, equipment and medium
CA2454740C (en) Storage medium encoded with a server program and method using same
CN115525305A (en) Data processing method, application starting method, device, computer equipment and storage medium
US11017032B1 (en) Document recovery utilizing serialized data
CN107577825A (en) A kind of method and device in mobile terminal loading webpage
US12032516B1 (en) File-level snapshot access service
CN114296730A (en) Page information processing method and device and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20221223