CN113536185A - Application page loading method, storage medium and related equipment thereof - Google Patents
Application page loading method, storage medium and related equipment thereof Download PDFInfo
- Publication number
- CN113536185A CN113536185A CN202110857091.0A CN202110857091A CN113536185A CN 113536185 A CN113536185 A CN 113536185A CN 202110857091 A CN202110857091 A CN 202110857091A CN 113536185 A CN113536185 A CN 113536185A
- Authority
- CN
- China
- Prior art keywords
- page
- access request
- application
- browser
- target
- 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.)
- Granted
Links
- 238000011068 loading method Methods 0.000 title claims abstract description 50
- 238000009877 rendering Methods 0.000 claims abstract description 55
- 230000000977 initiatory effect Effects 0.000 claims abstract description 8
- 238000000034 method Methods 0.000 claims description 45
- 238000012545 processing Methods 0.000 claims description 42
- 238000011161 development Methods 0.000 description 25
- 230000009286 beneficial effect Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 9
- 230000000694 effects Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application belongs to the technical field of computers, and relates to a loading method of an application page, which comprises the following steps: initiating an access request for a page of a target application to a server by adopting a browser; obtaining a target page file returned by the server according to the access request after the server determines that the access request is valid, wherein the target page file comprises public page content and proprietary page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the proprietary page content is page content which is specific to each page of each application, and the header component and the NavMenu component are both packaged in a general module definition specification umd format; and rendering and displaying the target page file by adopting the browser. The application also provides a loading system, terminal equipment, a server, computer equipment and a storage medium of the application page.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and a system for loading an application page, a terminal device, a server, a computer device, and a storage medium.
Background
With the increasing number of management applications developed based on various purposes, due to the various reasons that many projects are on-line in the early stage, the consideration is not thorough, the personnel change is changed, and the like, and the factors of technical updating and the like, the management application forms are different, the login forms are also different, different applications need to be switched back and forth when different functions are accessed, and the user is inconvenient to use.
At this time, a demand for integrating these management applications is naturally raised, but at present, the Javascript language commonly used in front-end development does not support "class" and "module", so that it is difficult to refer to module codes across different projects. Therefore, modules with the same function or capable of being shared theoretically among different projects still need to be repeatedly developed and deployed, and development efficiency is not improved.
Disclosure of Invention
An object of the embodiments of the present application is to provide an application page loading method, an application page loading system, a terminal device, a server, a computer device, and a storage medium, which are mainly used to improve development efficiency in developing a plurality of application pages in the prior art.
In order to solve the foregoing technical problem, a first aspect of the embodiments of the present application provides a method for loading an application page, where the method for loading the application page may include:
initiating an access request for a page of a target application to a server by adopting a browser;
obtaining a target page file returned by the server according to the access request after determining that the access request is valid, wherein the target page file may include public page content and proprietary page content, the public page content may include a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the proprietary page content is page content specifically possessed by respective pages of the applications, and the header component and the NavMenu component are both packaged in a format of a universal module definition specification umd;
and rendering and displaying the target page file by adopting the browser.
In order to solve the foregoing technical problem, a second aspect of the embodiments of the present application provides another method for loading an application page, where the method for loading an application page may include:
obtaining and storing public page content set for pages of a plurality of different applications, wherein the public page content can comprise a header component and a NavMenu component shared by the pages of the plurality of different applications, and the header component and the NavMenu component are both packaged in a general module definition specification umd format;
acquiring an access request sent by a browser for a page of a target application, and judging whether the access request is valid;
when the access request is determined to be valid, a target page file is determined according to the access request, and the target page file is returned to the browser, so that the browser performs rendering display processing on the target page file, wherein the target page file can comprise the public page content and the proprietary page content, and the proprietary page content is the page content specifically possessed by each application page.
In order to solve the foregoing technical problem, a third aspect of the embodiments of the present application provides another method for loading an application page, where the method for loading an application page may include:
the method comprises the steps that a server acquires and stores public page content set for pages of a plurality of different applications, wherein the public page content can comprise a header component and a NavMenu component which are shared by the pages of the plurality of different applications, and the header component and the NavMenu component are packaged in a general module definition specification umd format;
the terminal equipment initiates an access request to a page of a target application to the server by adopting a browser;
the server acquires an access request for a page of a target application sent by a browser and judges whether the access request is valid or not;
when the server determines that the access request is valid, a target page file is determined according to the access request, and the target page file is returned to the browser, wherein the target page file can comprise public page content and proprietary page content, and the proprietary page content is page content specifically possessed by each application page;
and the terminal equipment adopts the browser to perform rendering display processing on the target page file.
In order to solve the foregoing technical problem, a fourth aspect of the embodiments of the present application provides a terminal device, where the terminal device may include:
the sending module is used for initiating an access request to a page of a target application to a server by adopting a browser;
a receiving module, configured to obtain a target page file returned by the server according to the access request after determining that the access request is valid, where the target page file may include public page content and proprietary page content, the public page content may include a shared header component and a navigation menu NavMenu component that are set in advance for pages of multiple different applications, the proprietary page content is page content that is specific to respective pages of the applications, and the header component and the NavMenu component are both encapsulated in a format of a general module definition specification umd;
and the display module is used for rendering and displaying the target page file by adopting the browser.
In order to solve the above technical problem, a fifth aspect of embodiments of the present application provides a server, where the server may include:
the storage module is used for acquiring and storing public page content set for pages of a plurality of different applications, the public page content can comprise a header component and a NavMenu component which are shared by the pages of the plurality of different applications, and the header component and the NavMenu component are both packaged in a general module definition specification umd format;
the judging module is used for acquiring an access request for a page of a target application sent by a browser and judging whether the access request is valid or not;
and the sending module is used for determining a target page file according to the access request and returning the target page file to the browser when the access request is determined to be valid, so that the browser performs rendering display processing on the target page file, wherein the target page file can comprise the public page content and proprietary page content, and the proprietary page content is the page content specifically possessed by each application page.
In order to solve the foregoing technical problem, a sixth aspect of the present application embodiment provides a loading system for an application page, where the loading system for an application page includes:
a terminal device as described in the fourth aspect above and a server as described in the fifth aspect above.
In order to solve the foregoing technical problem, a seventh aspect of the embodiments of the present application further provides a computer device, which adopts the following technical solutions:
a computer device comprising a memory having computer readable instructions stored therein and a processor which when executed implements the steps of a method of loading an application page as claimed in any one of the first, second or third aspects.
In order to solve the foregoing technical problem, an eighth aspect of the embodiments of the present application further provides a computer-readable storage medium, which adopts the following technical solutions:
a computer readable storage medium having computer readable instructions stored thereon which, when executed by a processor, implement the steps of a method of loading an application page as claimed in any one of the first, second or third aspects.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, after the browser is adopted to initiate an access request to a page of a target application to a server, a target page file returned by the server according to the access request after the access request is determined to be valid can be obtained. And then, rendering and displaying the target page file by adopting the browser. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the Universal Module Definition (UMD) is a Javascript module specification, the effect that the packaged module code can be reused among different projects can be achieved after the code is packaged according to the module specification. Therefore, the content of the public page can be reused among different applications, repeated development of the part of codes is avoided, and development efficiency is improved.
Drawings
In order to more clearly illustrate the solution of the present application, the drawings needed for describing the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of a method for loading an application page according to the present application;
FIG. 3 is a flow diagram of yet another embodiment of a method for loading an application page according to the present application;
FIG. 4 is a flow diagram of yet another embodiment of a method for loading an application page according to the present application;
FIG. 5 is a block diagram of one embodiment of a terminal device 500 according to the present application;
FIG. 6 is a schematic block diagram illustrating one embodiment of a server 600 in accordance with the present application;
FIG. 7 is a schematic block diagram illustrating one embodiment of a loading system 700 for application pages in accordance with the present application;
FIG. 8 is a block diagram illustrating one embodiment of a computer device 800 according to the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background server providing support for pages displayed on the terminal devices 101, 102, 103.
It should be noted that the loading method of the application page provided in the embodiment of the present application is generally executed by a server/terminal device.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continuing reference to fig. 2, a method for loading an application page according to a flowchart of an embodiment of a method for loading an application page of the present application is shown, including the following steps:
step S201, a browser is adopted to initiate an access request to a page of a target application to a server.
In this embodiment, the loading method of the application page may be executed on an electronic device (for example, the terminal device shown in fig. 1) on which the electronic device may perform data interaction with the server through a wired connection manner or a wireless connection manner. After the http connection between the electronic device and the server is established, the electronic device may initiate an access request to a page of the target application to the server through a browser module embedded in a browser application or other types of applications.
Step S202, after the server determines that the access request is valid, a target page file returned according to the access request is obtained, wherein the target page file comprises public page content and proprietary page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the proprietary page content is page content which is specific to each page of each application, and the header component and the NavMenu component are both packaged in a general module definition specification umd format.
In this embodiment, after receiving the access request, the server may determine whether the access request is valid according to the link address in the access request. And after the link address is determined to be valid, inquiring and determining a target page file indicated by the link address, and returning the target page file to the electronic equipment. In order to reduce repeated development of the same content in the pages corresponding to different applications and unify style styles among different applications, the target page file, i.e. the HTML file, may include two parts, namely public page content and proprietary page content. The public page content comprises a shared header component and a NavMenu component, wherein the shared header component is preset for pages of a plurality of different applications, the NavMenu component is used for providing navigation for the pages and functions, the special page content is page content specific to each application, and the header component and the NavMenu component are packaged in the umd format of a general module definition specification.
Specifically, because the current web page is more and more like a desktop program, and the Javascript code embedded in the web page is more and more huge and more complex, a developer has to use a software engineering method, such as modular programming, to manage the service logic of the web page and improve the development efficiency. Through modular programming, developers only need to realize the service logic of the core, and other modules written by others can be loaded. However, Javascript is not a modular programming language, and does not support "class" and "module", so that most Javascript programs are non-modular programming. When the application is not in modular programming, all component files in a certain application page normally need to be placed under a large directory of the application, such as js files corresponding to a header component and a NavMenu component. Thus, if multiple applications have the same components on their pages, those components also need to be repeatedly deployed under the directories of the multiple applications, and after each modification.
Based on the above situation, various Javascript module specifications are currently defined, and developers can implement "class modular programming" of Javascript by following the Javascript module specification to develop and package codes. The UMD is a Javascript module specification, and the modules are a group of methods for realizing specific functions.
In the embodiment of the application, in order to realize the sharing of the public page content among the webpages of multiple applications, both the header component and the NavMenu component in the public page content are packaged in umd format. The encapsulated JS file can be deployed independently without being deployed in directories of all applications, so that cross-module and cross-application reference can be realized, and the deployment is simpler.
Step S203, a browser is used to perform rendering display processing on the target page file.
In this embodiment, after receiving the target page file, the browser may be used to analyze the code of the target page file, and then perform rendering and display processing on the target page file. During rendering, the browser executes codes in the target page file line by line, and sequentially executes processes of building a dom tree, building a rendering (render) tree, laying out the render tree, drawing the render tree and the like to generate and display a page view. Specifically, a rendering engine of the browser firstly analyzes a target page file, namely an html file, and converts the tags into dom nodes in the content tree according to the structure of the tags under the body attribute. And then, further analyzing the style information in the external CSS file and the style label. These style information, as well as the visibility instructions in html, will be used to build another tree, the render tree. The Render tree consists of rectangles containing attributes such as color and size, which are to be displayed on the screen in the correct order. After the Render tree is built, the rendering engine performs a layout process that determines the exact coordinates of each node on the screen. And the next step is drawing, namely traversing the render tree and drawing each node by using the UI back-end layer. It should be noted that this process is done step by step, and for better user experience, the rendering engine will render the content on the screen as early as possible, and will not wait until all html has been parsed and the render tree is built and laid out. It displays a part of the content after parsing a part of the content, and may download the rest of the content through the network.
In some possible implementation manners of the embodiment of the present application, the step of performing rendering and display processing on the target page file by using the browser includes: analyzing the codes in the target page file by adopting the browser, and triggering to initiate an XHR request for the head assembly and the NavMenu assembly to the server when analyzing the codes corresponding to the public page content; and receiving the header component and the NavMenu component returned by the server, and rendering and displaying the header component, the NavMenu component and the proprietary page content.
In the embodiment of the application, specifically, during rendering, when the browser parses a code corresponding to the public page content in the target page file, an xhr (xml Http request) request for the header component and the NavMenu component may be triggered to be initiated to the server. And then, after the header component and the NavMenu component returned by the server are received, rendering and displaying the header component, the NavMenu component and the proprietary page content.
In some possible implementation manners of the embodiment of the present application, after the step of initiating, by using the browser, an access request to a page of the target application to the server, the loading method further includes: receiving a public page file returned after the server determines that the access request is invalid, wherein the public page file is a preset page file shared by a plurality of different applications and comprises a shared login page file or an error processing page file; and rendering and displaying the public page file by adopting a browser.
Specifically, in order to unify style styles among webpages of multiple applications, it may be further configured that the multiple applications have a common pagefile, and the common pagefile may include a common login page file or an error handling page file. After the access request is sent to the server through the browser, if the server determines that the access request is invalid, the access request is directed to the public page file, and the public page file is returned to the browser. And then, the browser performs rendering display processing on the public page file. Because the common login page file or the error processing page file is adopted, the style styles among the webpages of a plurality of applications can be unified, the repeated development of the pages for different applications is avoided, and the development efficiency is improved.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, after the browser is adopted to initiate an access request to a page of a target application to a server, a target page file returned by the server according to the access request after the access request is determined to be valid can be obtained. And then, rendering and displaying the target page file by adopting the browser. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the content of the public page can be reused among different applications, repeated development of the part of codes is avoided, and development efficiency is improved.
With continuing reference to FIG. 3, a method for loading an application page is shown in a flowchart according to one embodiment of a method for loading an application page of the present application, comprising the steps of:
step S301, obtaining and storing public page content set for multiple pages of different applications, where the public page content includes a header component and a NavMenu component shared by the multiple pages of different applications, and both the header component and the NavMenu component are packaged in a general module definition specification umd format.
In this embodiment, the loading method of the application page may be executed on a server on which the application page is loaded, and the server may perform data interaction with the electronic device in a wired connection manner or a wireless connection manner. The server is configured by the external device, for example, public page content set by the external device for pages of a plurality of different applications can be acquired and stored, and the public page content includes a header component and a NavMenu component shared by the pages of the plurality of different applications.
Step S302, acquiring an access request for a page of a target application sent by a browser, and determining whether the access request is valid.
In the embodiment of the application, after the http connection is established between the electronic device and the server, the electronic device may initiate an access request to a page of a target application to the server through a browser module embedded in a browser application or other types of applications. The browser then determines whether the access request is valid.
In some possible implementation manners of the embodiment of the present application, the step of obtaining an access request sent by a browser to a page of a target application, and determining whether the access request is valid includes: acquiring an access request of a page of a target application sent by a browser, and extracting an application identifier of the target application in the access request; inquiring whether the page file of the target application can be matched or not according to the application identifier by adopting a reverse proxy server ngnix; if the matching is successful, determining a target page file according to the link address query carried in the query access request; judging whether the token of the target page file is valid; if the token is valid, determining that the access request is valid; and if the matching is unsuccessful or the token is invalid, determining that the access request is invalid.
Specifically, in the embodiment of the present application, the following settings need to be performed first: (1) modifying the packing webpack configuration for each old application, and adding a unique application prefix as a unique identifier for each application, such as/A,/B,/C and the like; (2) and a reverse proxy server ngnix is added and used for matching application paths such as/A and the like, so that the access request can jump to each application page after the access request is determined to be valid. At this time, after receiving the access request, the server may first extract the link address, such as/a/home address, in the access request, and query whether the "/a" application identifier is configured in ngnix in advance, that is, query whether the page file of the a application can be matched. And if the matching can be obtained, further inquiring and obtaining the target page file guided by the link address. And then extracting the token of the target page file, judging whether the token is effective, namely whether the token exists or is overdue, and if the token is effective, determining that the access request is effective. And if the matching is unsuccessful or the token fails, determining that the access request fails. The reverse proxy server is arranged on the server to proxy the access request sent by the external browser, so that the load of the network and the server can be reduced, the access efficiency is improved, and in addition, whether the target webpage file is effective or not is further judged through the token, and the safety of the server can be further improved.
Step S303, when the access request is determined to be valid, determining a target page file according to the access request, and returning the target page file to the browser, so that the browser performs rendering display processing on the target page file, wherein the target page file comprises public page content and proprietary page content, and the proprietary page content is page content specifically possessed by each application page.
In the embodiment of the application, after the server determines that the access request is valid through the steps, the server returns the target page file determined according to the link address query in the access request to the browser. Therefore, after the browser receives the target page file, the browser can be used for analyzing the code of the target page file, and then rendering and displaying the target page file. During rendering, the browser executes codes in the target page file line by line, and sequentially executes processes of building a dom tree, building a render tree, laying out the render tree, drawing the render tree and the like to generate and display a page view.
In some possible implementation manners of the embodiment of the present application, when it is determined that the access request is valid, determining a target page file according to the access request, and returning the target page file to the browser, so that the browser performs rendering and display processing on the target page file, including: when the access request is determined to be valid, determining a target page file according to the access request, and returning the target page file to the browser; when a code corresponding to public page content in a target page file is analyzed by a browser, an initiated XHR request for a header component and a NavMenu component is triggered; and sending the head component and the NavMenu component to the browser so that the browser performs rendering display processing on the head component, the NavMenu component and the proprietary page content.
Specifically, in the embodiment of the present application, in order to implement sharing of public page content among webpages of multiple applications, both the header component and the NavMenu component in the public page content are packaged in umd format. The encapsulated JS file can be deployed in a server independently without being deployed in directories of various applications, so that cross-module and cross-application reference can be realized, and the deployment is simpler. Specifically, during rendering, when the browser parses a code corresponding to the public page content in the target page file, an xhr (xml Http request) request for the header component and the NavMenu component may be triggered to be initiated to the server. And then, the server inquires and determines a head component and a JS file corresponding to the NavMenu component, and returns the JS file to the browser, so that the browser performs rendering display processing on the head component, the NavMenu component and the proprietary page content.
In some possible implementation manners of the embodiment of the present application, before the steps of obtaining an access request sent by a browser to a page of a target application and determining whether the access request is valid, the loading method further includes: acquiring and storing a public page file, wherein the public page file is a preset page file shared by a plurality of different applications and comprises a shared login page file or an error processing page file; after the steps of obtaining an access request for a page of a target application sent by a browser and judging whether the access request is valid, the loading method further includes: and when the access request is determined to be invalid, returning the public page file to the browser so that the browser performs rendering display processing on the public page file.
In the embodiment of the present application, the following settings need to be performed first: (1) deleting the login page and the error processing page of each application, and modifying all paths which point to the login page and the error processing page and are jumped to a preset public page file, wherein the public page file comprises a common login page file or an error processing page file, and the paths are/main/login,/main/404,/main/502 and the like; (2) and adding a reverse proxy server ngnix which is used for the path of the public pagefile, so that the access request can jump to the path of the public pagefile after being determined to be invalid. At this time, after receiving the access request, the server may automatically jump the link address of the access request to the path of the public pagefile by the foregoing determination method if it is determined that the access request is invalid. And then, the server extracts the public page file and returns the public page file to the browser, so that the browser performs rendering display processing on the public page file.
It is emphasized that, to further ensure the privacy and security of the public pagefile, the public pagefile may also be stored in a node of a blockchain.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, after receiving an access request initiated by a browser and addressed to a page of a target application, a server may determine whether the access request is valid, and if so, return the target page file to the browser according to the access request, so that the browser performs rendering display processing on the target page file. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the public page content can realize the multiplexing of a plurality of applications, the repeated development of the part of codes is avoided, and the development efficiency is improved.
With continuing reference to fig. 4, a method for loading an application page according to a flowchart of an embodiment of a method for loading an application page of the present application is shown, including the following steps:
step S401, the server obtains and stores public page content set for the pages of the multiple different applications, the public page content comprises a header component and a NavMenu component shared by the pages of the multiple different applications, and the header component and the NavMenu component are packaged in a general module definition specification umd format.
Step S402, the terminal device adopts the browser to initiate an access request to the page of the target application to the server.
In step S403, the server obtains an access request for a page of the target application sent by the browser, and determines whether the access request is valid.
Step S404, when the server determines that the access request is valid, the server determines a target page file according to the access request, and returns the target page file to the browser, wherein the target page file comprises public page content and proprietary page content, and the proprietary page content is page content specifically possessed by each application page.
Step S405, the terminal device adopts the browser to perform rendering display processing on the target page file.
It should be noted that step S401, step S403, and step S404 are similar to step S301, step S302, and step S303 in the foregoing embodiment shown in fig. 3, respectively, and step S402 and step S405 are similar to step S201 and step S203 in the foregoing embodiment shown in fig. 2, respectively, and are not repeated here again.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, after receiving an access request to a page of a target application initiated by a terminal device through a browser, a server can determine whether the access request is valid, and if so, returns the target page file to the browser according to the access request, so that the browser performs rendering display processing on the target page file. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the public page content can realize the multiplexing of a plurality of applications, the repeated development of the part of codes is avoided, and the development efficiency is improved.
The application is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware associated with computer readable instructions, which can be stored in a computer readable storage medium, and when executed, the processes of the embodiments of the methods described above can be included. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
With further reference to fig. 5, as an implementation of the method shown in fig. 2, the present application provides an embodiment of a terminal device, and as shown in fig. 5, the terminal device 500 according to this embodiment includes:
a sending module 501, configured to initiate an access request for a page of a target application to a server by using a browser;
a receiving module 502, configured to obtain a target page file returned by the server according to the access request after determining that the access request is valid, where the target page file includes public page content and proprietary page content, the public page content includes a shared header component and a navigation menu NavMenu component that are preset for pages of multiple different applications, the proprietary page content is page content that is specific to respective pages of the applications, and the header component and the NavMenu component are both encapsulated in a format of a general module definition specification umd;
a display module 503, configured to perform rendering and display processing on the target page file by using the browser.
In some possible implementation manners of the embodiment of the present application, the display module 503 includes:
the analysis submodule is used for analyzing the codes in the target page file by adopting the browser, and triggering to initiate an XHR request to the head assembly and the NavMenu assembly to the server when analyzing the codes corresponding to the public page content;
and the rendering submodule is used for receiving the header component and the NavMenu component returned by the server and rendering and displaying the header component, the NavMenu component and the proprietary page content.
In some possible implementation manners of the embodiment of the present application, the display module 503 is further configured to receive a public page file returned by the server after determining that the access request is invalid, where the public page file is a page file that is preset and is shared by a plurality of different applications, and the public page file includes a shared login page file or an error handling page file;
the display module 503 is further configured to perform rendering display processing on the public page file by using the browser.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, after the terminal device initiates an access request to a page of a target application to a server by using a browser, a target page file returned by the server according to the access request after the server determines that the access request is valid can be obtained. And then, rendering and displaying the target page file by adopting the browser. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the public page content can realize the multiplexing of a plurality of applications, the repeated development of the part of codes is avoided, and the development efficiency is improved.
With further reference to fig. 6, as an implementation of the method shown in fig. 3, the present application provides an embodiment of a server, and as shown in fig. 6, the server 600 according to this embodiment includes:
the storage module 601 is configured to acquire and store public page content set for pages of multiple different applications, where the public page content includes a header component and a NavMenu component that are shared by the pages of the multiple different applications, and both the header component and the NavMenu component are encapsulated in a format of a universal module definition specification umd;
a determining module 602, configured to obtain an access request for a page of a target application, where the access request is sent by a browser, and determine whether the access request is valid;
a sending module 603, configured to determine, when it is determined that the access request is valid, a target page file according to the access request, and return the target page file to the browser, so that the browser performs rendering display processing on the target page file, where the target page file includes the public page content and a proprietary page content, and the proprietary page content is page content specifically possessed by each respective page of each application.
In some possible implementation manners of the embodiment of the present application, the sending module 603 includes:
the first sending submodule is used for determining a target page file according to the access request and returning the target page file to the browser when the access request is determined to be effective;
the receiving submodule is used for triggering an initiated XHR request for the header component and the NavMenu component when the browser analyzes the code corresponding to the public page content in the target page file;
and the second sending submodule is used for sending the header component and the NavMenu component to the browser so that the browser can perform rendering display processing on the header component, the NavMenu component and the proprietary page content.
In some possible implementations of the embodiments of the present application,
the storage module 601 is further configured to obtain and store a public page file, where the public page file is a page file shared by a plurality of preset different applications, and the public page file includes a shared login page file or an error processing page file;
the sending module 603 is further configured to, when it is determined that the access request is invalid, return the public pagefile to the browser, so that the browser performs rendering and display processing on the public pagefile.
In some possible implementations of the embodiment of the present application, the determining module 602 includes
The extraction submodule is used for acquiring an access request sent by a browser for a page of a target application and extracting an application identifier of the target application in the access request;
the reverse proxy submodule is used for inquiring whether the page file of the target application can be matched or not according to the application identifier by adopting a reverse proxy server ngnix;
the query submodule is used for querying and determining a target page file according to the link address carried in the query access request if the matching is successful;
the judgment submodule is used for judging whether the token of the target page file is valid or not; if the token is valid, determining that the access request is valid; if the match is unsuccessful or the token is invalid, the access request is determined to be invalid.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, after receiving an access request initiated by a browser and addressed to a page of a target application, a server may determine whether the access request is valid, and if so, return the target page file to the browser according to the access request, so that the browser performs rendering display processing on the target page file. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the public page content can realize the multiplexing of a plurality of applications, the repeated development of the part of codes is avoided, and the development efficiency is improved.
With further reference to fig. 7, as an implementation of the method shown in fig. 4, the present application provides an embodiment of a loading system for an application page, and as shown in fig. 7, a loading system 700 for an application page according to this embodiment includes:
a terminal device 500 as described in the embodiment shown in fig. 5 above and a server 600 as described in the embodiment shown in fig. 6 above.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, after receiving an access request to a page of a target application initiated by a terminal device through a browser, a server can determine whether the access request is valid, and if so, returns the target page file to the browser according to the access request, so that the browser performs rendering display processing on the target page file. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the public page content can realize the multiplexing of a plurality of applications, the repeated development of the part of codes is avoided, and the development efficiency is improved.
In order to solve the technical problem, an embodiment of the present application further provides a computer device. Referring to fig. 8, fig. 8 is a block diagram of a basic structure of a computer device according to the present embodiment.
The computer device 800 includes a memory 801, a processor 802, and a network interface 803 communicatively coupled to each other via a system bus. It is noted that only a computer device 800 having components 801 and 803 is shown, but it is understood that not all of the shown components are required and that more or fewer components can alternatively be implemented. As will be understood by those skilled in the art, the computer device is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and the hardware includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like.
The computer device can be a desktop computer, a notebook, a palm computer, a cloud server and other computing devices. The computer equipment can carry out man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch panel or voice control equipment and the like.
The memory 801 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 801 may be an internal storage unit of the computer apparatus 800, such as a hard disk or a memory of the computer apparatus 800. In other embodiments, the memory 801 may also be an external storage device of the computer device 800, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like provided on the computer device 800. Of course, the memory 801 may also include both internal and external memory units of the computer device 800. In this embodiment, the memory 801 is generally used to store an operating system and various types of application software installed on the computer device 800, such as the computer readable instructions of the loading method of the application page described in fig. 2, fig. 3, or fig. 4. In addition, the memory 801 can also be used to temporarily store various types of data that have been output or are to be output.
The processor 802 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 802 generally operates to control the overall operation of the computer device 800. In this embodiment, the processor 802 is configured to execute computer readable instructions stored in the memory 801 or process data, for example, execute computer readable instructions of the loading method of the application page.
The network interface 803 may include a wireless network interface or a wired network interface, and the network interface 803 is generally used to establish a communication link between the computer device 800 and other electronic devices.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in the embodiment of the application, when the computer executes the computer readable instruction, after receiving an access request to a page of a target application initiated by a terminal device through a browser, the computer may determine whether the access request is valid, and if the access request is valid, return the target page file to the browser according to the access request, so that the browser performs rendering and display processing on the target page file. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the public page content can realize the multiplexing of a plurality of applications, the repeated development of the part of codes is avoided, and the development efficiency is improved.
The present application further provides another embodiment, which is to provide a computer-readable storage medium storing computer-readable instructions executable by at least one processor to cause the at least one processor to perform the steps of the method for loading an application page as described in fig. 2, fig. 3 or fig. 4 above.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects:
in this embodiment of the application, the computer readable instructions may be executed by at least one processor, and after receiving an access request to a page of a target application, initiated by a terminal device through a browser, the computer readable instructions may determine whether the access request is valid, and if the access request is valid, return the target page file to the browser according to the access request, so that the browser performs rendering display processing on the target page file. The target page file comprises public page content and special page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the special page content is page content which is specific to each application, and the header component and the NavMenu component are packaged in the umd format of a universal module definition specification. Because the UMD is a Javascript module specification, after the code is packaged according to the module specification, the effect that the packaged module code can be reused among different projects can be realized. Therefore, the public page content can realize the multiplexing of a plurality of applications, the repeated development of the part of codes is avoided, and the development efficiency is improved.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as 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 application.
It is to be understood that the above-described embodiments are merely illustrative of some, but not restrictive, of the broad invention, and that the appended drawings illustrate preferred embodiments of the invention and do not limit the scope of the invention. This application is capable of embodiments in many different forms and is provided for the purpose of enabling a thorough understanding of the disclosure of the application. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to one skilled in the art that the present application may be practiced without modification or with equivalents of some of the features described in the foregoing embodiments. All equivalent structures made by using the contents of the specification and the drawings of the present application are directly or indirectly applied to other related technical fields and are within the protection scope of the present application.
Claims (11)
1. A method for loading an application page is characterized by comprising the following steps:
initiating an access request for a page of a target application to a server by adopting a browser;
obtaining a target page file returned by the server according to the access request after the server determines that the access request is valid, wherein the target page file comprises public page content and proprietary page content, the public page content comprises a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the proprietary page content is page content which is specific to each page of each application, and the header component and the NavMenu component are both packaged in a general module definition specification umd format;
and rendering and displaying the target page file by adopting the browser.
2. The method for loading the application page according to claim 1, wherein the step of rendering and displaying the target page file by using the browser includes:
analyzing the codes in the target page file by adopting the browser, and triggering to initiate an XHR request for the head assembly and the NavMenu assembly to the server when analyzing the codes corresponding to the public page content;
and receiving the header component and the NavMenu component returned by the server, and rendering and displaying the header component, the NavMenu component and the proprietary page content.
3. The loading method of the application page according to claim 1 or 2, wherein after the step of initiating the access request to the page of the target application to the server by using the browser, the loading method further comprises:
receiving a public page file returned by the server after the server determines that the access request is invalid, wherein the public page file is a preset page file shared by a plurality of different applications and comprises a shared login page file or an error processing page file;
and rendering and displaying the public page file by adopting the browser.
4. A method for loading an application page is characterized by comprising the following steps:
the method comprises the steps of obtaining and storing public page content set for pages of a plurality of different applications, wherein the public page content comprises a header component and a NavMenu component which are shared by the pages of the plurality of different applications, and the header component and the NavMenu component are packaged in a general module definition specification umd format;
acquiring an access request sent by a browser for a page of a target application, and judging whether the access request is valid;
and when the access request is determined to be valid, determining a target page file according to the access request, and returning the target page file to the browser so that the browser performs rendering display processing on the target page file, wherein the target page file comprises public page content and proprietary page content, and the proprietary page content is page content specifically possessed by each application page.
5. The method for loading the application page according to claim 4, wherein when it is determined that the access request is valid, the step of determining a target page file according to the access request and returning the target page file to the browser so that the browser performs rendering and display processing on the target page file comprises:
when the access request is determined to be valid, determining a target page file according to the access request, and returning the target page file to the browser;
when the browser analyzes the code corresponding to the public page content in the target page file, triggering and initiating an XHR request for the head assembly and the NavMenu assembly;
and sending the head component and the NavMenu component to the browser so that the browser performs rendering display processing on the head component, the NavMenu component and the proprietary page content.
6. The loading method of the application page according to claim 4 or 5, wherein before the steps of obtaining an access request sent by a browser for a page of a target application and determining whether the access request is valid, the loading method further comprises:
acquiring and storing a public page file, wherein the public page file is a preset page file shared by a plurality of different applications and comprises a shared login page file or an error processing page file;
after the step of obtaining an access request sent by a browser for a page of a target application and determining whether the access request is valid, the loading method further includes:
and when the access request is determined to be invalid, returning the public page file to the browser so that the browser performs rendering display processing on the public page file.
7. The method for loading the application page according to claim 4 or 5, wherein the step of obtaining the access request for the page of the target application sent by the browser and determining whether the access request is valid comprises:
acquiring an access request of a page of a target application sent by a browser, and extracting an application identifier of the target application in the access request;
adopting a reverse proxy server ngnix to inquire whether the page file of the target application can be matched or not according to the application identifier;
if the matching is successful, determining a target page file according to the link address query carried in the query access request;
judging whether the token of the target page file is valid;
if the token is valid, determining that the access request is valid;
and if the matching is unsuccessful or the token is invalid, determining that the access request is invalid.
8. A terminal device, comprising:
the sending module is used for initiating an access request to a page of a target application to a server by adopting a browser;
a receiving module, configured to obtain a target page file returned by the server according to the access request after determining that the access request is valid, where the target page file includes public page content and proprietary page content, the public page content includes a shared header component and a navigation menu NavMenu component that are preset for pages of multiple different applications, the proprietary page content is page content that is specific to each page of each application, and the header component and the NavMenu component are both packaged in a format of a universal module definition specification umd;
and the display module is used for rendering and displaying the target page file by adopting the browser.
9. A server, comprising:
the storage module is used for acquiring and storing public page content set for pages of a plurality of different applications, the public page content comprises a header component and a NavMenu component which are shared by the pages of the plurality of different applications, and the header component and the NavMenu component are packaged in a general module definition specification umd format;
the judging module is used for acquiring an access request sent by a browser for a page of a target application and judging whether the access request is valid or not;
and the sending module is used for determining a target page file according to the access request and returning the target page file to the browser when the access request is determined to be valid, so that the browser performs rendering display processing on the target page file, wherein the target page file comprises public page content and proprietary page content, and the proprietary page content is page content specifically possessed by each application page.
10. A computer device comprising a memory having computer readable instructions stored therein and a processor which when executed implements the steps of the method of loading an application page as claimed in any one of claims 1 to 3, or claims 4 to 7.
11. A computer-readable storage medium, having computer-readable instructions stored thereon, which, when executed by a processor, implement the steps of the method of loading an application page as claimed in any one of claims 1 to 3, or claims 4 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110857091.0A CN113536185B (en) | 2021-07-28 | 2021-07-28 | Application page loading method, storage medium and related equipment |
| PCT/CN2022/071877 WO2023005163A1 (en) | 2021-07-28 | 2022-01-13 | Method for loading application page, storage medium and related device thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110857091.0A CN113536185B (en) | 2021-07-28 | 2021-07-28 | Application page loading method, storage medium and related equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113536185A true CN113536185A (en) | 2021-10-22 |
| CN113536185B CN113536185B (en) | 2024-01-02 |
Family
ID=78121223
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110857091.0A Active CN113536185B (en) | 2021-07-28 | 2021-07-28 | Application page loading method, storage medium and related equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113536185B (en) |
| WO (1) | WO2023005163A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114217864A (en) * | 2021-11-02 | 2022-03-22 | 北京健康之家科技有限公司 | Dynamic access method and device of application, storage medium and computer equipment |
| WO2023005163A1 (en) * | 2021-07-28 | 2023-02-02 | 平安科技（深圳）有限公司 | Method for loading application page, storage medium and related device thereof |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116466953B (en) * | 2023-03-03 | 2024-01-02 | 港珠澳大桥管理局 | Modularized front-end development method, device, computer equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104346463A (en) * | 2014-11-07 | 2015-02-11 | 北京奇虎科技有限公司 | Loading method and device of page label and browser client |
| CN108846087A (en) * | 2018-06-12 | 2018-11-20 | 恒生电子股份有限公司 | A kind of page rendering method, apparatus, terminal and server |
| CN109491653A (en) * | 2018-11-21 | 2019-03-19 | 泰康保险集团股份有限公司 | Component sharing method under micro services framework, device, electronic equipment |
| US20190098096A1 (en) * | 2017-09-28 | 2019-03-28 | Citrix Systems, Inc. | Managing Browser Session Navigation Between One Or More Browsers |
| CN111159595A (en) * | 2019-12-24 | 2020-05-15 | 平安养老保险股份有限公司 | Page loading method, system, computer equipment and computer readable storage medium |
| CN111209028A (en) * | 2020-01-07 | 2020-05-29 | 京东数字科技控股有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN112817591A (en) * | 2021-01-26 | 2021-05-18 | 山东浪潮通软信息科技有限公司 | Front-end page construction method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111339455B (en) * | 2018-12-18 | 2024-02-23 | 阿里巴巴集团控股有限公司 | Method and device for loading page first screen by browser application |
| CN113536185B (en) * | 2021-07-28 | 2024-01-02 | 平安科技（深圳）有限公司 | Application page loading method, storage medium and related equipment |
-
2021
- 2021-07-28 CN CN202110857091.0A patent/CN113536185B/en active Active
-
2022
- 2022-01-13 WO PCT/CN2022/071877 patent/WO2023005163A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104346463A (en) * | 2014-11-07 | 2015-02-11 | 北京奇虎科技有限公司 | Loading method and device of page label and browser client |
| US20190098096A1 (en) * | 2017-09-28 | 2019-03-28 | Citrix Systems, Inc. | Managing Browser Session Navigation Between One Or More Browsers |
| CN108846087A (en) * | 2018-06-12 | 2018-11-20 | 恒生电子股份有限公司 | A kind of page rendering method, apparatus, terminal and server |
| CN109491653A (en) * | 2018-11-21 | 2019-03-19 | 泰康保险集团股份有限公司 | Component sharing method under micro services framework, device, electronic equipment |
| CN111159595A (en) * | 2019-12-24 | 2020-05-15 | 平安养老保险股份有限公司 | Page loading method, system, computer equipment and computer readable storage medium |
| CN111209028A (en) * | 2020-01-07 | 2020-05-29 | 京东数字科技控股有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN112817591A (en) * | 2021-01-26 | 2021-05-18 | 山东浪潮通软信息科技有限公司 | Front-end page construction method and device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023005163A1 (en) * | 2021-07-28 | 2023-02-02 | 平安科技（深圳）有限公司 | Method for loading application page, storage medium and related device thereof |
| CN114217864A (en) * | 2021-11-02 | 2022-03-22 | 北京健康之家科技有限公司 | Dynamic access method and device of application, storage medium and computer equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113536185B (en) | 2024-01-02 |
| WO2023005163A1 (en) | 2023-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113536185B (en) | Application page loading method, storage medium and related equipment | |
| CN111414407A (en) | Data query method and device of database, computer equipment and storage medium | |
| CN112416458A (en) | Preloading method and device based on ReactNative, computer equipment and storage medium | |
| CN113382083B (en) | Webpage screenshot method and device | |
| CN113377373A (en) | Page loading method and device based on analysis engine, computer equipment and medium | |
| CN108494762A (en) | Web access method, device and computer readable storage medium, terminal | |
| CN112650905A (en) | Anti-crawler method and device based on label, computer equipment and storage medium | |
| CN112631924A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN114996619A (en) | Page display method and device, computer equipment and storage medium | |
| CN113268245A (en) | Code analysis method, device and storage medium | |
| CN112860662A (en) | Data blood relationship establishing method and device, computer equipment and storage medium | |
| CN113315829B (en) | Client offline H5 page loading method and device, computer equipment and medium | |
| CN113282591B (en) | Authority filtering method, authority filtering device, computer equipment and storage medium | |
| CN113434254B (en) | Client deployment method, client deployment apparatus, computer device, and storage medium | |
| CN112965721B (en) | Project compiling method and device based on Android, computer equipment and storage medium | |
| CN111797297B (en) | Page data processing method and device, computer equipment and storage medium | |
| CN109684570A (en) | Web information processing method and device | |
| CN113127783B (en) | Page display method and device, equipment and medium | |
| CN114912003A (en) | Document searching method and device, computer equipment and storage medium | |
| CN114090066A (en) | User interface card view generation method and device, computer equipment and medium | |
| CN115562662A (en) | Application page creating method and device, computer equipment and storage medium | |
| CN114968822A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN115203672A (en) | Information access control method and device, computer equipment and medium | |
| CN115525305A (en) | Data processing method, application starting method, device, computer equipment and storage medium | |
| CN107798023A (en) | Web page resources loading method and web page resources loading device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |