CN113536185B - Application page loading method, storage medium and related equipment - Google Patents
Application page loading method, storage medium and related equipment Download PDFInfo
- Publication number
- CN113536185B CN113536185B CN202110857091.0A CN202110857091A CN113536185B CN 113536185 B CN113536185 B CN 113536185B CN 202110857091 A CN202110857091 A CN 202110857091A CN 113536185 B CN113536185 B CN 113536185B
- Authority
- CN
- China
- Prior art keywords
- page
- access request
- browser
- component
- application
- 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.)
- Active
Links
- 238000011068 loading method Methods 0.000 title claims abstract description 51
- 238000009877 rendering Methods 0.000 claims abstract description 49
- 230000000977 initiatory effect Effects 0.000 claims abstract description 8
- 238000000034 method Methods 0.000 claims description 34
- 238000012545 processing Methods 0.000 claims description 33
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000011161 development Methods 0.000 description 26
- 230000009286 beneficial effect Effects 0.000 description 9
- 230000000694 effects Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression 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
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 235000019800 disodium phosphate Nutrition 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
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (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 to a page of a target application to a server by adopting a browser; after the server determines that the access request is effective, a target page file returned according to the access request is acquired, wherein the target page file comprises public page contents and private page contents, the public page contents comprise a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the private page contents are page contents which are specific to respective pages of each application, and the header component and the NavMenu component are 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 disclosure relates to the field of computer technologies, and in particular, to a method for loading an application page, 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 for various purposes, because many projects are rapidly brought on line in the early stage, various reasons such as insufficient and thorough consideration, personnel variation and the like, and factors such as technology updating and substitution, the management applications are different in form, the login forms are also different, different applications need to be switched back and forth to access different functions, and users are inconvenient to use.
At this time, naturally, the requirements of integrating these management applications are raised, but the Javascript language commonly adopted by front-end development at present does not support "class" and "module", so that the introduction of module codes across items is difficult to realize between different items. Therefore, modules with the same functions or which can be used in common in theory are caused among different projects, and repeated development and deployment are still needed, so that development efficiency is not improved.
Disclosure of Invention
The embodiment of the application aims to provide an application page loading method, an application page loading system, terminal equipment, a server, computer equipment and a storage medium, and the application page loading method, the application page loading system, the terminal equipment, the server, the computer equipment and the storage medium are mainly used for improving development efficiency in developing pages of a plurality of applications in the prior art.
In order to solve the above technical problem, a first aspect of an embodiment of the present application provides a method for loading an application page, where the method for loading an application page may include:
initiating an access request to a page of a target application to a server by adopting a browser;
after the server determines that the access request is effective, a target page file returned according to the access request is acquired, wherein the target page file can comprise public page content and private page content, the public page content can comprise a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd;
and rendering and displaying the target page file by adopting the browser.
In order to solve the above technical problem, a second aspect of the embodiments of the present application provides another application page loading method, where the application page loading method may include:
acquiring and storing public page contents set for pages of a plurality of different applications, wherein the public page contents 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 format of a general module definition specification umd;
Acquiring an access request sent by a browser to a page of a target application, and judging whether the access request is effective or not;
and when the access request is determined to be effective, determining a target page file according to the access request, and returning the target page file to the browser so as to enable the browser to conduct rendering display processing on the target page file, wherein the target page file can comprise the public page content and the special page content, and the special page content is page content which is specific to each page of each application.
In order to solve the above technical problem, a third aspect of the embodiments of the present application provides another application page loading method, where the application page loading method may include:
the server acquires and stores public page contents set for pages of a plurality of different applications, wherein the public page contents 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 format of a general module definition specification umd;
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 of a page of a target application sent by a browser and judges whether the access request is effective;
When the server determines that the access request is effective, determining a target page file according to the access request, and returning the target page file to the browser, wherein the target page file can comprise the public page content and the private page content, and the private page content is page content which is specific to each page of each application;
and the terminal equipment adopts the browser to render and display the target page file.
In order to solve the above technical problem, a fourth aspect of the embodiments of the present application provides a terminal device, which may include:
the sending module is used for initiating an access request to a page of the target application to the server by adopting the browser;
the receiving module is used for acquiring a target page file returned by the server according to the access request after the server determines that the access request is effective, wherein the target page file can comprise public page content and private page content, the public page content can comprise a shared head header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the private page content is page content which is specific to each page of each application, and the head component and the NavMenu component are packaged 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, which may include:
the storage module is used for acquiring and storing public page contents set for pages of a plurality of different applications, wherein the public page contents 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 format of a general module definition specification umd;
the judging module is used for acquiring an access request of a page of the target application sent by the browser and judging whether the access request is effective or not;
and the sending module is used for determining a target page file according to the access request when the access request is determined to be effective, and returning the target page file to the browser so as to enable the browser to conduct rendering display processing on the target page file, wherein the target page file can comprise the public page content and the special page content, and the special page content is page content which is specific to each page of each application.
In order to solve the above technical problem, a sixth aspect of the embodiments of the present application provides a loading system of an application page, where the loading system of the 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 above technical problem, a seventh aspect of the embodiments of the present application further provides a computer device, which adopts the following technical scheme:
a computer device comprising a memory having stored therein computer readable instructions which when executed implement the steps of the method of loading application pages of any of the first, second or third aspects.
In order to solve the above technical problem, an eighth aspect of the embodiments of the present application further provides a computer readable storage medium, which adopts the following technical scheme:
a computer readable storage medium having stored thereon computer readable instructions which when executed by a processor implement the steps of the method of loading application pages of any one of the first, second or third aspects.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in the embodiment of the application, after the browser is adopted to initiate the access request to the page of the target application to the server, the target page file returned by the server according to the access request after the server determines that the access request is effective 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 private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since the universal module definition specification (universal module definition, UMD) is a Javascript module specification, the effect that packaged module code can be reused among different items can be achieved after the code is packaged in compliance with the module specification. Therefore, the public page content can realize multiplexing among different applications, repeated development of the part of codes is avoided, and development efficiency is improved.
Drawings
For a clearer description of the solution in the present application, a brief description will be given below of the drawings that are needed in the description of the embodiments of the present application, it being obvious that the drawings in the following description are some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow chart of one embodiment of a method of loading an application page according to the present application;
FIG. 3 is a flow chart of yet another embodiment of a method of loading an application page according to the present application;
FIG. 4 is a flow chart of yet another embodiment of a method of loading an application page according to the present application;
fig. 5 is a schematic structural diagram of one embodiment of a terminal device 500 according to the present application;
FIG. 6 is a schematic diagram of the architecture of one embodiment of a server 600 according to the present application;
FIG. 7 is a structural schematic diagram of one embodiment of a loading system 700 of an application page according to the present application;
fig. 8 is a schematic structural diagram of 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 applications herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description and claims of the present application and in the description of the figures above are intended to cover non-exclusive inclusions. The terms first, second and the like in the description and in the claims or in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases 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. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In order to better understand the technical solutions of the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and 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 application page loading method 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 continued reference to fig. 2, there is shown a method of loading an application page according to a flowchart of one embodiment of the method of loading an application page of the present application, comprising the steps of:
in step S201, an access request for a page of a target application is initiated to a server by using a browser.
In this embodiment, the loading method of the application page may be run on an electronic device (for example, a terminal device shown in fig. 1) thereon, where the electronic device may perform data interaction with the server through a wired connection manner or a wireless connection manner. After the electronic device establishes http connection with the server, the electronic device may initiate an access request to a page of the target application to the server through a browser application or a browser module embedded in other types of applications.
Step S202, after determining that the access request is valid, the obtaining server returns a target page file according to the access request, wherein the target page file comprises public page contents and private page contents, the public page contents comprise a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the private page contents are page contents which are specific to respective pages of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd.
In this embodiment, after receiving the access request, the server may first determine whether the access request is valid according to the link address in the access request. After determining that the link address is valid, querying a target page file indicated by the determined link address, and returning the target page file to the electronic device. In order to reduce repeated development of the same part of content in pages corresponding to different applications and unify style among different applications, the target page file, namely the HTML file, can comprise two parts of public page content and private page content. The public page content comprises a shared header component which is preset for pages of a plurality of different applications and a NavMenu component which is used for providing navigation for the pages and the functions, the private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd.
Specifically, as the current web page is more and more like a desktop program, the Javascript code embedded in the web page is more and more huge and more complex, so that a developer has to use a software engineering method, such as modularized programming, to manage the business logic of the web page, thereby improving the development efficiency. Through modularized programming, a developer only needs to realize the business logic of the core, and other modules which are written by others can be loaded. Javascript is not a modular programming language, however, and does not support "classes" and "modules", so Javascript programming is mostly non-modular programming. When in non-modular programming, all component files in a normal certain application page, such as js files corresponding to a header component and a NavMenu component, need to be placed under a large directory of the application. Thus, if pages of multiple applications have the same components, those components also need to be redeployed under the catalog of the multiple applications, and redeployed after each modification.
Based on the above situation, there are currently defined various Javascript module specifications, and a developer can implement "class modular programming" of Javascript by following the Javascript module specifications to develop and code package. The UMD is a specification of a Javascript module, which is a set of methods for implementing specific functions.
In the embodiment of the application, in order to realize sharing of public page content among web pages of a plurality of applications, a 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 the catalogue of each application, so that cross-module and cross-application reference can be realized, and the deployment is simpler.
And step S203, rendering and displaying the target page file by adopting a browser.
In this embodiment, after receiving the target page file, the browser may be used to parse the code of the target page file, and further perform rendering and display processing on the target page file. When rendering, the browser executes codes in the target page file row by row, and sequentially executes the processes of building a dom tree, building a rendering (render) tree, laying out the render tree, drawing the render tree and the like, so as to generate and display a page view. Specifically, the rendering engine of the browser first parses the target page file, i.e., html file, and converts these tags into dom nodes in the content tree according to the structure of the tags under the body attribute. Then, style information in the external CSS file and style tag is further parsed. These style information and visibility instructions in html will be used to construct another tree, the render tree. The Render tree consists of rectangles containing attributes such as color and size that will be displayed on the screen in the correct order. After the Render tree is built, the rendering engine will perform a layout process that will determine the exact coordinates of each node on the screen. The next step is to draw, i.e., traverse the render tree and draw each node using the UI backend layers. It should be noted that this process is done gradually, and for better user experience, the rendering engine will render the content onto the screen as early as possible, and will not wait until all html is parsed to complete before building and laying out the render tree. It displays a part of the content after parsing the part of the content, and may download the rest of the content through the network.
In some possible implementations of the embodiments of the present application, the step of performing rendering display processing on the target page file using the browser includes: analyzing codes in the target page file by adopting the browser, and triggering to initiate XHR requests for the header component and the NavMenu component to the server when analyzing 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, particularly, when the browser parses the code corresponding to the public page content in the target page file during rendering, the initiation of the XHR (XML Http Request) request to the header component and the NavMenu component to the server may be triggered. And then, rendering and displaying the header component, the NavMenu component and the proprietary page content after receiving the header component and the NavMenu component returned by the server.
In some possible implementations of the embodiments of the present application, after the step of initiating, with the browser, an access request to the server for the page of the target application, the loading method further includes: the method comprises the steps that a public page file returned after an invalid access request is determined by a receiving server, 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.
In particular, to unify style patterns among web pages of multiple applications, multiple applications may also be configured to have a common public page file, which may include a common log-in page file or an error handling page file. After sending the access request 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 shared login page file or the error processing page file is adopted, style patterns among the webpages of a plurality of applications can be unified, repeated development of the webpages for different applications is avoided, and development efficiency is improved.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in the embodiment of the application, after the browser is adopted to initiate the access request to the page of the target application to the server, the target page file returned by the server according to the access request after the server determines that the access request is effective 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 private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing among different applications, repeated development of the part of codes is avoided, and development efficiency is improved.
With continued reference to fig. 3, there is shown a method of loading an application page of a flowchart according to one embodiment of the method of loading an application page of the present application, comprising the steps of:
in step S301, public page contents set for pages of a plurality of different applications are obtained and stored, where the public page contents include a header component and a NavMenu component that are shared by the pages of the plurality of different applications, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd.
In this embodiment, the loading method of the application page may run on a server on which the application page may perform data interaction with the electronic device through a wired connection manner or a wireless connection manner. The server is configured through the external device, for example, public page contents set by the external device for pages of a plurality of different applications can be obtained and stored, and the public page contents comprise a header component and a NavMenu component which are shared by the pages of the plurality of different applications.
Step S302, an access request of a page of a target application sent by a browser is obtained, and whether the access request is valid or not is judged.
In the embodiment of the application, after the electronic device establishes the http connection with the server, the electronic device may initiate an access request to a page of the target application to the server through a browser application or a browser module embedded in other types of applications. The browser then determines whether the access request is valid.
In some possible implementations of the embodiments of the present application, 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 include: 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 can be matched with the target application 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 a 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, then the access request is determined to be invalid.
Specifically, in the embodiment of the present application, the following settings are first required: (1) Modifying the packed weback configuration for each legacy application, adding a unique application prefix as a unique identifier for each application, such as/A,/B,/C, etc.; (2) And adding a reverse proxy server ngnix for matching/A and other application paths, so that the access request can jump to each application page after being determined to be valid. At this time, after receiving the access request, the server may first extract the link address, e.g., the/a/home address, in the access request, and query whether the "/a" application identifier is configured in ngnix in advance, i.e., whether the query can be matched to the page file of the a application. If the target page file can be obtained by matching, further inquiring and acquiring the target page file guided by the link address. And then extracting the token of the target page file, judging whether the token is valid, namely whether the token exists and is out of date, and if so, determining that the access request is valid. 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, 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 effective, determining a target page file according to the access request, and returning the target page file to the browser so as to enable the browser to render and display the target page file, wherein the target page file comprises public page content and private page content, and the private page content is page content which is specific to each page of each application.
In this embodiment of the present application, after determining that the access request is valid through the above steps, the server returns, to the browser, the target page file determined according to the link address query in the access request. Therefore, after the browser receives the target page file, the browser can be adopted to analyze the code of the target page file, and further render and display the target page file. When rendering, the browser executes codes in the target page file row by row, and sequentially executes the processes of building a dom tree, building a render tree, laying out the render tree, drawing the render tree and the like, so as to generate and display a page view.
In some possible implementations of the embodiments of the present application, when determining 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 display processing on the target page file, including: when the access request is determined to be effective, determining a target page file according to the access request, and returning the target page file to the browser; triggering initiated XHR requests for a header component and a NavMenu component when a browser analyzes codes corresponding to public page contents in a target page file; and sending the header component and the NavMenu component to the browser, so that the browser can render and display the header component, the NavMenu component and the proprietary page content.
Specifically, in the embodiment of the present application, in order to realize sharing of public page content among web pages of multiple applications, a header component and the NavMenu component in the public page content are both encapsulated in umd format. The encapsulated JS file can be deployed in a server independently without being deployed in the catalogue of each application, so that cross-module and cross-application reference can be realized, and the deployment is simpler. Specifically, when the browser parses the code corresponding to the public page content in the target page file during rendering, the method can trigger a XHR (XML Http Request) request to the server for the header component and the NavMenu component. And then, the server inquires and determines JS files corresponding to the header component and the NavMenu component, and returns the JS files to the browser, so that the browser performs rendering display processing on the header component, the NavMenu component and the special page content.
In some possible implementations of the embodiments of the present application, before the step of obtaining the access request sent by the browser to the page of the 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 acquiring the access request of the page of the target application sent by the browser and judging whether the access request is valid or not, the loading method further comprises the following steps: and when the access request is determined to be invalid, returning the public page file to the browser so that the browser can render and display the public page file.
In the embodiment of the present application, the following settings are first needed: (1) Deleting the login page and the error processing page of each application, and modifying all paths which jump to the login page and point to the error processing page as preset public page files, wherein the public page files comprise shared login page files or error processing page files, and the paths are such as/main/logic,/main/404,/main/502 and the like; (2) And adding a reverse proxy server ngnix which is used for the path of the public page file, so that the access request can jump to the path of the public page file after being determined to be invalid. In this case, after receiving the access request, the server may automatically jump the link address of the access request to the path of the common page file if it is determined that the access request is invalid by the above-described determination method. 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 blockchain node.
The blockchain referred to in the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, an application services layer, and the like.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in this embodiment of the present application, after receiving an access request to a target application page initiated by a browser, a server may determine whether the access request is valid, and if so, return, to the browser, the target page file 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 private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing of a plurality of applications, repeated development of the part of codes is avoided, and development efficiency is improved.
With continued reference to fig. 4, there is shown a method of loading an application page according to a flowchart of one embodiment of the method of loading an application page of the present application, comprising the steps of:
in step S401, the server obtains and stores public page contents set for pages of a plurality of different applications, where the public page contents include a header component and a NavMenu component that are shared by the pages of the plurality of different applications, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd.
In step S402, the terminal device initiates an access request to the page of the target application to the server by using the browser.
In step S403, the server obtains the access request sent by the browser to the page of the target application, and determines whether the access request is valid.
In step S404, when the server determines 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, where the target page file includes public page content and private page content, and the private page content is page content that is specific to each page of each application.
In step S405, the terminal device performs rendering display processing on the target page file by using a browser.
It should be noted that, the step S401, the step S403, and the step S404 are similar to the step S301, the step S302, and the step S303 in the embodiment shown in fig. 3, and the step S402 and the step S405 are similar to the step S201 and the step S203 in the embodiment shown in fig. 2, respectively, and detailed descriptions thereof are omitted herein.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in this embodiment of the present application, after receiving an access request to a target application page initiated by a terminal device through a browser, a server may determine whether the access request is valid, and if so, return, to the browser, the target page file 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 private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing of a plurality of applications, repeated development of the part of codes is avoided, and development efficiency is improved.
The subject application is operational with numerous general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet 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.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by computer readable instructions stored in a computer readable storage medium that, when executed, may comprise the steps of the embodiments of the methods described above. The storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a random access Memory (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, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the flowcharts of the figures may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily being sequential, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.
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, as shown in fig. 5, a terminal device 500 according to the present embodiment includes:
a sending module 501, configured to initiate, with a browser, an access request to a page of a target application to a server;
a receiving module 502, configured to obtain, after determining that the access request is valid, a target page file returned according to the access request, where the target page file includes public page content and private page content, the public page content includes a shared header component and a navigation menu NavMenu component that are preset for pages of a plurality of different applications, the private 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 general module definition specification umd;
And the display module 503 is used for rendering and displaying the target page file by adopting the browser.
In some possible implementations of the embodiments of the present application, the display module 503 includes:
the analysis sub-module is used for analyzing codes in the target page file by adopting the browser, and triggering to initiate XHR requests for the header component and the NavMenu component to the server when analyzing codes corresponding to the public page content;
and the rendering sub-module 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 special page content.
In some possible implementations of the embodiments of the present application, the display module 503 is further configured to receive a public page file returned after the server determines that the access request is invalid, 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 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 has the following main beneficial effects:
In the embodiment of the application, after the terminal device initiates the access request to the page of the target application to the server by adopting the browser, the target page file returned by the server according to the access request after the server determines that the access request is effective 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 private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing of a plurality of applications, repeated development of the part of codes is avoided, and 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, as shown in fig. 6, where the server 600 includes:
A storage module 601, configured to obtain and store public page contents set for pages of a plurality of different applications, where the public page contents include a header component and a NavMenu component that are shared by the pages of the plurality of different applications, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd;
a judging module 602, configured to obtain an access request sent by a browser to a page of a target application, and judge whether the access request is valid;
and the sending module 603 is configured to determine a target page file according to the access request when the access request is determined to be valid, 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 the private page content, and the private page content is page content that is specific to each page of each application.
In some possible implementations of the embodiments of the present application, the sending module 603 includes:
the first sending sub-module is used for determining a target page file according to the access request when the access request is determined to be effective, and returning the target page file to the browser;
The receiving sub-module is used for triggering an initiated XHR request for the header component and the NavMenu component when the browser analyzes codes corresponding to the public page content in the target page file;
and the second sending sub-module is used for sending the header component and the NavMenu component to the browser so that the browser can render and display the header component, the NavMenu component and the special page content.
In some possible implementations of embodiments of the present application,
the storage module 601 is further configured to acquire 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 handling page file;
and the sending module 603 is further configured to return the public page file to the browser when the access request is determined to be invalid, so that the browser performs rendering display processing on the public page file.
In some possible implementations of the embodiments of the present application, the determining module 602 includes
The extraction sub-module is used for 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;
The reverse proxy sub-module is used for inquiring whether the page file of the target application can be matched or not according to the application identification by adopting a reverse proxy server ngnix;
the inquiring sub-module is used for inquiring and determining a target page file according to the link address carried in the inquiring access request if the matching is successful;
the judging 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 has the following main beneficial effects:
in this embodiment of the present application, after receiving an access request to a target application page initiated by a browser, a server may determine whether the access request is valid, and if so, return, to the browser, the target page file 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 private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing of a plurality of applications, repeated development of the part of codes is avoided, and 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 an application page loading system, as shown in fig. 7, where an application page loading system 700 according to the present 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 has the following main beneficial effects:
in this embodiment of the present application, after receiving an access request to a target application page initiated by a terminal device through a browser, a server may determine whether the access request is valid, and if so, return, to the browser, the target page file 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 private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing of a plurality of applications, repeated development of the part of codes is avoided, and development efficiency is improved.
In order to solve the technical problems, the embodiment of the application also provides computer equipment. Referring specifically to fig. 8, fig. 8 is a basic structural block diagram 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 should be noted that only computer device 800 having components 801-803 is shown in the figures, but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead. It will be appreciated by those skilled in the art that the computer device herein is a device capable of automatically performing numerical calculations and/or information processing in accordance with predetermined or stored instructions, the hardware of which includes, but is not limited to, microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASICs), programmable gate arrays (fields-Programmable Gate Array, FPGAs), digital processors (Digital Signal Processor, DSPs), embedded devices, etc.
The computer equipment can be a desktop computer, a notebook computer, a palm computer, a cloud server and other computing equipment. The computer equipment can perform man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch pad or voice control equipment and the like.
The memory 801 includes at least one type of readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 801 may be an internal storage unit of the computer device 800, such as a hard disk or a memory of the computer device 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, which are provided on the computer device 800. Of course, the memory 801 may also include both internal storage elements of the computer device 800 and external storage devices. In this embodiment, the memory 801 is typically used to store an operating system and various application software installed on the computer device 800, such as computer readable instructions of the application page loading method described in fig. 2, 3 or 4. Further, 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 (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 802 is generally used 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, such as computer readable instructions for executing a loading method of the application page.
The network interface 803 may include a wireless network interface or a wired network interface, the network interface 803 typically being used to establish a communication connection between the computer device 800 and other electronic devices.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in this embodiment of the present application, when executing the computer readable instruction, after receiving an access request to a target application page initiated by a terminal device through a browser, the computer may determine whether the access request is valid, and if so, return, according to the access request, the target page file to the browser, so that the browser performs rendering display processing on the target page file. The target page file comprises public page content and private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing of a plurality of applications, repeated development of the part of codes is avoided, and development efficiency is improved.
The present application also provides another embodiment, namely, 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, 3 or 4 above.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in this embodiment of the present application, the computer readable instructions may be executed by at least one processor, and after receiving an access request for 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 so, return, according to the access request, the target page file to the browser, so that the browser performs rendering display processing on the target page file. The target page file comprises public page content and private page content, wherein 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 private page content is page content which is specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd. Since UMD is a Javascript module specification, after code is packed in compliance with the module specification, the effect that packed module code can be reused among different projects can be achieved. Therefore, the public page content can realize multiplexing of a plurality of applications, repeated development of the part of codes is avoided, and development efficiency is improved.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
It is apparent that the embodiments described above are only some embodiments of the present application, but not all embodiments, the preferred embodiments of the present application are given in the drawings, but not limiting the patent scope of the present application. This application may be embodied in many different forms, but rather, embodiments are provided in order to provide a more thorough understanding of the present disclosure. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that modifications may be made to the embodiments described in the foregoing, or equivalents may be substituted for elements thereof. All equivalent structures made by the specification and the drawings of the application are directly or indirectly applied to other related technical fields, and are also within the protection scope of the application.
Claims (9)
1. The application page loading method is characterized by comprising the following steps of:
initiating an access request to a page of a target application to a server by adopting a browser, wherein the server is used for determining whether the access request is effective or not according to a link address in the received access request;
after the server determines that the access request is effective, a target page file returned according to the access request is acquired, wherein the target page file comprises public page contents and private page contents, the public page contents comprise a shared header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the private page contents are page contents which are specific to respective pages of each application, and the header component and the NavMenu component are packaged in a general module definition specification umd format;
rendering and displaying the target page file by adopting the browser;
the step of rendering and displaying the target page file by adopting the browser comprises the following steps:
analyzing codes in the target page file by adopting the browser, and triggering to initiate XHR requests for the header component and the NavMenu component to the server when analyzing 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.
2. The method for loading application pages according to claim 1, wherein after the step of initiating an access request to the server for the page of the target application using the browser, the method for loading application pages further comprises:
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 the browser.
3. The application page loading method is characterized by comprising the following steps of:
acquiring and storing public page contents set for pages of a plurality of different applications, wherein the public page contents 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 format of a general module definition specification umd;
Acquiring an access request sent by a browser to a page of a target application, and judging whether the access request is effective or not;
when the access request is determined to be effective, determining a target page file according to the access request, and returning the target page file to the browser so that the browser can render and display the target page file, wherein the target page file comprises the public page content and the special page content, and the special page content is page content which is specific to each page of each application;
and when the access request is determined to be effective, 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 method comprises the following steps of:
when the access request is determined to be effective, determining a target page file according to the access request, and returning the target page file to the browser;
triggering an initiated XHR request for the header component and the NavMenu component when the browser analyzes codes corresponding to the public page content in the target page file;
And sending the header component and the NavMenu component to the browser, so that the browser performs rendering display processing on the header component, the NavMenu component and the proprietary page content.
4. The application page loading method according to claim 3, wherein before the step of acquiring an access request to a page of a target application sent by a browser 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 the access request sent by the browser to the page of the target application and judging whether the access request is valid, the loading method further comprises the following steps:
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.
5. The application page loading method according to claim 3, wherein the step of obtaining an access request to a page of a target application sent by a browser and determining whether the access request is valid comprises:
Acquiring an access request sent by a browser to a page of a target application, and extracting an application identifier of the target application in the access request;
inquiring whether the page file can be matched with the target application 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 or not;
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.
6. A terminal device, comprising:
the system comprises a sending module, a server and a receiving module, wherein the sending module is used for initiating an access request of a page of a target application to the server by adopting a browser, and the server is used for determining whether the access request is valid or not according to a link address in the received access request;
the receiving module is used for acquiring a target page file returned by the server according to the access request after the server determines that the access request is effective, wherein the target page file comprises public page contents and private page contents, the public page contents comprise a shared head header component and a navigation menu NavMenu component which are preset for pages of a plurality of different applications, the private page contents are page contents which are specific to each page of each application, and the header component and the NavMenu component are packaged in a format of a general module definition specification umd;
The display module is used for rendering and displaying the target page file by adopting the browser;
the display module 503 includes:
the analysis sub-module is used for analyzing codes in the target page file by adopting the browser, and triggering to initiate XHR requests for the header component and the NavMenu component to the server when analyzing codes corresponding to the public page content;
and the rendering sub-module 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 special page content.
7. A server, comprising:
the storage module is used for acquiring and storing public page contents set for pages of a plurality of different applications, wherein the public page contents 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 format of a general module definition specification umd;
the judging module is used for acquiring an access request of a page of the target application sent by the browser and judging whether the access request is effective or not;
the sending module is used for determining a target page file according to the access request when the access request is determined to be effective, and returning the target page file to the browser so that the browser can render and display the target page file, wherein the target page file comprises the public page content and the private page content, and the private page content is page content which is specific to each page of each application;
The transmitting module 603 includes:
the first sending sub-module is used for determining a target page file according to the access request when the access request is determined to be effective, and returning the target page file to the browser;
the receiving sub-module is used for triggering an initiated XHR request for the header component and the NavMenu component when the browser analyzes codes corresponding to the public page content in the target page file;
and the second sending sub-module is used for sending the header component and the NavMenu component to the browser so that the browser can render and display the header component, the NavMenu component and the special page content.
8. A computer device comprising a memory having stored therein computer readable instructions which when executed implement the steps of the loading method of application pages as claimed in any one of claims 1 to 2 or 3 to 5.
9. A computer readable storage medium, characterized in that it has stored thereon computer readable instructions which, when executed by a processor, implement the steps of the loading method of application pages according to claims 1 to 2 or any of claims 3-5.
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 CN113536185A (en) | 2021-10-22 |
| CN113536185B true 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) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113536185B (en) * | 2021-07-28 | 2024-01-02 | 平安科技（深圳）有限公司 | Application page loading method, storage medium and related equipment |
| CN114217864A (en) * | 2021-11-02 | 2022-03-22 | 北京健康之家科技有限公司 | Dynamic access method and device of application, storage medium and computer equipment |
| CN114185537A (en) * | 2021-12-06 | 2022-03-15 | 招联消费金融有限公司 | Page processing method and device, computer equipment and storage medium |
| CN116466953B (en) * | 2023-03-03 | 2024-01-02 | 港珠澳大桥管理局 | Modularized front-end development method, device, computer equipment and storage medium |
Citations (6)
| 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 |
| 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 (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10693974B2 (en) * | 2017-09-28 | 2020-06-23 | Citrix Systems, Inc. | Managing browser session navigation between one or more browsers |
| 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 (6)
| 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 |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023005163A1 (en) | 2023-02-02 |
| CN113536185A (en) | 2021-10-22 |
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 | |
| CN106406844B (en) | Method and device for realizing public number menu of communication interaction platform | |
| CN112416458A (en) | Preloading method and device based on ReactNative, computer equipment and storage medium | |
| CN108494762A (en) | Web access method, device and computer readable storage medium, terminal | |
| CN112631924A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN111552463A (en) | Page jump method and device, computer equipment and storage medium | |
| CN113282591B (en) | Authority filtering method, authority filtering device, computer equipment and storage medium | |
| CN116569165B (en) | Page display method and device, storage medium and electronic equipment | |
| CN113157523B (en) | Service monitoring method and device, computer equipment and storage medium | |
| CN111797297B (en) | Page data processing method and device, computer equipment and storage medium | |
| CN111158777B (en) | Component calling method, device and computer readable storage medium | |
| CN116304403A (en) | Webpage access method and device, computer equipment and storage medium | |
| CN113127783B (en) | Page display method and device, equipment and medium | |
| CN114912003A (en) | Document searching method and device, computer equipment and storage medium | |
| CN112416875B (en) | Log management method, device, computer equipment and storage medium | |
| CN114090066A (en) | User interface card view generation method and device, computer equipment and medium | |
| CN113760274A (en) | Front-end component logic injection method and device | |
| CN112948727B (en) | WebView-based data injection method, device, equipment and storage medium | |
| CN116108814B (en) | Gantt chart processing method and device, computer equipment and storage medium | |
| CN115795209A (en) | Method, device, equipment and medium for executing Eval function based on browser plug-in | |
| CN116467145A (en) | Page performance data acquisition method and device, computer equipment and storage medium | |
| CN117880008A (en) | Gateway-based service request processing method, device, equipment and storage medium | |
| CN117290019A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN117492752A (en) | Page dynamic configuration method and device, computer equipment and storage medium |
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 |