Sub-application page loading method and device, equipment and storage medium

Abstract

The application discloses a kind of sub-application page loading method, device, equipment and storage medium.The method comprises: in response to the access request of user to the business function of business item, according to the project resource address of business item, the hyper text markup file of the parent application of business item is loaded;At least one sub-application associated with the business function is determined by the environment parameter pre-configured in the hyper text markup file;The data exchange format file of each sub-application is loaded by the hyper text markup file;According to the data exchange format file of each sub-application, generate target routing address, so that the user accesses the page of sub-application associated with the business function based on the target routing address.The sub-application page loading efficiency of the embodiment technical scheme of the present application is improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, apparatus, device, and storage medium for loading sub-application pages. Background Technology

[0002] As current business projects become increasingly complex, with more and more features being implemented, the amount of code also increases, making project maintenance more difficult. Therefore, how to break down the various functional modules of a business project into different sub-applications and load, develop, and maintain them separately has become an urgent problem to be solved.

[0003] Existing methods for loading pages and maintaining code for sub-applications in a project are typically based on the micro-frontend framework qiankun. However, the qiankun micro-frontend framework has the following problems: the flexibility of page composition between sub-applications is low, and additional page jump overhead is required every time a sub-application is loaded, thereby reducing page loading speed. Summary of the Invention

[0004] This invention provides a method, apparatus, device, and storage medium for loading sub-application pages, in order to improve the loading efficiency of sub-application pages.

[0005] According to one aspect of the present invention, a method for loading a sub-application page is provided, the method comprising:

[0006] In response to a user's request to access the business functions of a business project, the hypertext markup file of the parent application of the business project is loaded according to the project resource address of the business project.

[0007] At least one sub-application associated with the business function is determined by using pre-configured environment parameters in the hypertext markup file;

[0008] The data exchange format files of each of the sub-applications are loaded using the hypertext markup file;

[0009] Based on the data exchange format files of each sub-application, a target routing address is generated so that the user can access the sub-application associated with the business function based on the target routing address.

[0010] According to another aspect of the present invention, a sub-application page loading device is provided, the device comprising:

[0011] The hypertext file loading module is used to respond to a user's access request for the business functions of a business project, and load the hypertext markup file of the parent application of the business project according to the project resource address of the business project.

[0012] The sub-application determination module is used to determine at least one sub-application associated with the business function based on pre-configured environment parameters in the hypertext markup file.

[0013] The format file determination module is used to load the data exchange format files of each of the sub-applications through the hypertext markup file;

[0014] The target route generation module is used to generate target route addresses based on the data exchange format files of each sub-application, so that the user can access the sub-applications associated with the business functions based on the target route addresses.

[0015] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0016] At least one processor; and

[0017] A memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the sub-application page loading method according to any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the sub-application page loading method according to any embodiment of the present invention.

[0020] This invention's technical solution responds to a user's access request for a business function of a business project by loading the hypertext markup file of the parent application of the business project based on the project resource address; determining at least one sub-application associated with the business function through pre-configured environment parameters in the hypertext markup file; loading the data exchange format files of each sub-application through the hypertext markup file; and generating a target routing address based on the data exchange format files of each sub-application, allowing the user to access the page of the sub-application associated with the business function based on the target routing address. This technical solution determines and loads the corresponding sub-applications by loading pre-configured environment parameters, and configures the sub-applications to be loaded under different environment functions as needed. This achieves flexible combination of sub-application pages for different business functions, thereby improving the loading efficiency of pages associated with business functions and avoiding the additional loading time overhead caused by switching between sub-application pages. By merging sub-application routes, the routes of sub-applications are combined into the actual routes required by the business function. When a user accesses a business function of a business project through a browser, the experience of switching between different sub-application pages is the same as switching within the same sub-application, with no additional overhead, smooth interaction, and improved user experience.

[0021] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a flowchart of a sub-application page loading method provided in Embodiment 1 of the present invention;

[0024] Figure 2 This is a flowchart of a sub-application page loading method provided in Embodiment 2 of the present invention;

[0025] Figure 3 This is a flowchart of a sub-application page loading method provided in Embodiment 3 of the present invention;

[0026] Figure 4 This is a schematic diagram of the structure of a sub-application page loading device according to Embodiment 4 of the present invention;

[0027] Figure 5This is a schematic diagram of the structure of an electronic device that implements the sub-application page loading method of this invention. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] Example 1

[0031] Figure 1 This is a flowchart of a sub-application page loading method provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of loading pages of sub-applications associated with the business functions of a business project. This method can be executed by a sub-application page loading device, which can be implemented in hardware and / or software. The sub-application page loading can be configured in an electronic device. Figure 1 As shown, the method includes:

[0032] S110. In response to a user's request to access the business functions of a business project, load the hypertext markup file of the parent application of the business project according to the project resource address of the business project.

[0033] The parent application can be the entry application for users to access business projects. When a user accesses a sub-application page corresponding to a business function of a business project, the parent application's hypertext markup file needs to be loaded first, and then the corresponding sub-application is loaded through the parent application's hypertext markup file.

[0034] A business project can include at least one business function. Different business functions can be associated with a parent application and at least one child application, i.e., an application combination between a parent application and at least one child application. A parent application or child application can contain multiple application pages. It should be noted that the child application pages associated with a business function can be one or more of the child application pages of the associated child application. For example, for a business function M, which is associated with parent application A and child applications B and C, child application B can include child application pages b1, b2, and b3; child application C can include child application pages c1 and c2. The child application pages associated with business function M can include child application pages b1, b3, and c2.

[0035] The project resource address for a business project can be a URL (Uniform Resource Locator). Access requests can be generated by users clicking on business function interfaces within the project. The access request may include the project resource address, which can be obtained by parsing the request.

[0036] The parent application's hypertext markup file can be the parent application's HTML (Hypertext Markup Language) file.

[0037] For example, in response to a user's click on the business function interface of a business project, an access request for the business function is generated; based on the project resource address of the business project carried in the access request, the root route is first accessed, and the Index.HTML file (hypertext markup file) of the parent application of the business project is loaded.

[0038] S120. Identify at least one sub-application associated with the business function using pre-configured environment parameters in a hypertext markup file.

[0039] It's important to note that existing technical solutions require loading the parent application first, then switching to and loading the sub-applications, and finally loading the corresponding sub-application pages when accessing sub-application pages via URL paths, thus incurring additional overhead. However, the sub-application pages associated with the business functions accessed by users are fixed. Therefore, we can pre-associate the sub-applications corresponding to each business function and pre-configure the association relationships and related parameter data in an environment parameter file. This allows us to directly retrieve the environment parameters when a user accesses a business function, determine the relevant sub-application page, and load it, reducing the overhead of page redirection or loading and improving page loading efficiency.

[0040] The environmental parameters can be pre-configured and generated by relevant technical personnel and stored in the parent application's hypertext markup file (Index.HTML).

[0041] In one optional embodiment, the environment parameters are configured as follows: determine at least one business function of the business project and determine the sub-applications associated with each business function; generate a functional application mapping relationship between each business function and the corresponding sub-application; configure the environment parameters according to the functional application mapping relationship and the application configuration parameters related to each sub-application.

[0042] Specifically, this can involve generating environment parameters that include functional application mapping relationships and application configuration parameters related to each sub-application. These application configuration parameters may include, for example, sub-application version numbers.

[0043] Understandably, to accommodate different business projects being deployed, placeholders can be added to the parent application's hypertext markup file (Index.HTML) for subsequent calls to the business functions of the corresponding business projects by sub-applications.

[0044] Optionally, the parent application's hypertext markup file includes at least one placeholder; the placeholder is used to represent different environmental parameters corresponding to different business projects. The form of the placeholder can be pre-defined by relevant technical personnel; for example, the placeholder can be "_config_". Specifically, the placeholder can be inserted into the corresponding position in the parent application's hypertext markup file by calling the API (Application Programming Interface) of UMI (Extensible Enterprise Front-End Application Framework).

[0045] S130. Load the data exchange format files of each sub-application through the hypertext markup file.

[0046] The parent application's hypertext markup file references the parent application's data exchange format file. This data exchange format file can be a JSON (JavaScript Object Notation) file, specifically an Index.JS file.

[0047] For example, the parent application's hypertext markup file is loaded to load the parent application's data exchange format file referenced in the hypertext markup file; the parent application's data exchange format file is parsed, and during the parsing process, the overridden page rendering method is called to load the data exchange format files (JS files) of each sub-application. The overridden page rendering method pre-configures methods for calling each sub-application, and these pre-configured methods call and load the data exchange format files of each sub-application.

[0048] S140. Generate target routing addresses based on the data exchange format files of each sub-application, so that users can access the pages of the sub-applications associated with the business functions based on the target routing addresses.

[0049] For example, by calling the route merging method pre-configured in the parent application's data exchange format file, the page routes of each sub-application can be merged based on their respective data exchange format files to obtain the target route address. This target route address is then fed back to the user, allowing them to select and access the appropriate sub-application page based on their page operations related to business functions. By using the target route address, the loading of the parent and sub-applications is chained together, eliminating the need to load sub-application pages across multiple browser windows and enabling access to different sub-application pages within the same browser window.

[0050] This invention's technical solution responds to a user's access request for a business function of a business project by loading the hypertext markup file of the parent application of the business project based on the project resource address; determining at least one sub-application associated with the business function through pre-configured environment parameters in the hypertext markup file; loading the data exchange format files of each sub-application through the hypertext markup file; and generating a target routing address based on the data exchange format files of each sub-application, allowing the user to access the page of the sub-application associated with the business function based on the target routing address. This technical solution determines and loads the corresponding sub-applications by loading pre-configured environment parameters, and configures the sub-applications to be loaded under different environment functions as needed. This achieves flexible combination of sub-application pages for different business functions, thereby improving the loading efficiency of pages associated with business functions and avoiding the additional loading time overhead caused by switching between sub-application pages. By merging sub-application routes, the routes of sub-applications are combined into the actual routes required by the business function. When a user accesses a business function of a business project through a browser, the experience of switching between different sub-application pages is the same as switching within the same sub-application, with no additional overhead, smooth interaction, and improved user experience.

[0051] Example 2

[0052] Figure 2 This is a flowchart illustrating a sub-application page loading method according to Embodiment 2 of the present invention. This embodiment is an optimization and improvement based on the above-described technical solutions.

[0053] Furthermore, the step "loading the data exchange format files of each sub-application via a hypertext markup file" is refined to "loading the data exchange format file of the parent application via a hypertext markup file; parsing the data exchange format file of the parent application, and calling the pre-configured page rendering method to load the data exchange format files of each sub-application during the file parsing process." This improves the method for loading the data exchange format files of sub-applications.

[0054] Furthermore, the step "generate the target route address based on the data exchange format file of each sub-application" is refined to "obtain the sub-route address of each sub-application based on the data exchange format file of each sub-application by calling the route acquisition method in the data exchange format file of the parent application; and merge the sub-route address of each sub-application with the root route address of the parent application by calling the route merging method in the data exchange format file of the parent application to obtain the target route address." This improves the method for generating the target route address.

[0055] It should be noted that for parts not described in detail in the embodiments of the present invention, please refer to the descriptions in other embodiments. For example... Figure 2 As shown, the method includes the following specific steps:

[0056] S210. In response to a user's request to access the business functions of a business project, load the hypertext markup file of the parent application of the business project according to the project resource address of the business project.

[0057] S220. Identify at least one sub-application associated with the business function using pre-configured environment parameters in a hypertext markup file.

[0058] S230. Load the data exchange format file of the parent application via the hypertext markup file.

[0059] The parent application's HTML file (Index.HTML) references the parent application's data exchange format file (Index.JS). Therefore, when the parent application's HTML file is loaded, the parent application's data exchange format file can also be loaded.

[0060] S240. Parse the data exchange format file of the parent application, and in the process of parsing the file, call the pre-configured page rendering method to load the data exchange format files of each sub-application.

[0061] The page rendering method can be pre-rewritten and configured in the parent application's data exchange format file by relevant technical personnel. The rewritten page rendering method can then call the data exchange format file of the sub-application.

[0062] In an optional embodiment, during the file parsing process, a pre-configured page rendering method is invoked to load the data exchange format files of each sub-application, including: during the file parsing process, the pre-configured page rendering method is invoked to call an asynchronous loader to obtain and load the data exchange format files of the sub-applications corresponding to the application version numbers from the static server based on the application version numbers of each sub-application.

[0063] The asynchronous loader can be an AMD (Asynchronous Module Definition) loader; the method for calling the asynchronous loader is pre-configured in the overridden page rendering method.

[0064] For example, during the file parsing process, the asynchronous loader is called through a pre-configured rewritten page rendering method to obtain and load the data exchange format file corresponding to the application version number of each sub-application from the static resource server.

[0065] It should be noted that asynchronous loader code conforming to the AMD specification can be injected with the UMI plugin. When the asynchronous loader is called to load a sub-application, the application version number JS file (module-version.js) is loaded first. Based on the application version number of each sub-application output in this file, the corresponding version of the sub-application's data exchange format file (JS file) is loaded from the static resource server.

[0066] The above technical solution, through pre-configured rewritten logic methods that conform to the asynchronous loader calling specification, and loading logic that includes the deployment application version of the sub-application, realizes the loading of data exchange format files of sub-applications associated with business functions. This solves the problem of long page loading time on the first visit when all business function code is in one application and a large number of data exchange format files are loaded for the first time.

[0067] S250. By calling the route acquisition method in the data exchange format file of the parent application, the sub-route address of each sub-application is obtained based on the data exchange format file of each sub-application.

[0068] For example, the sub-route addresses of each sub-application can be obtained by calling the getRoutes method in the data exchange format file of the parent application.

[0069] S260. By calling the route merging method in the data exchange format file of the parent application, the sub-route addresses of each sub-application and the root route address of the parent application are merged to obtain the target route address, so that users can access the pages of the sub-applications associated with the business functions based on the target route address.

[0070] For example, by calling the `patchRoutes` method, the sub-route addresses of each sub-route and the root route address of the parent application are merged to obtain the target route address. Users can then match and access the data exchange format file of the sub-application to be loaded based on the target route address.

[0071] This embodiment's technical solution loads the parent application's data exchange format file using a hypertext markup file, parses the parent application's data exchange format file, and calls a pre-configured page rendering method during the parsing process to load the data exchange format files of each sub-application. This achieves loading of data exchange format files of sub-applications related to business functions, avoiding the overhead of switching and loading between sub-applications. By calling the route acquisition method in the parent application's data exchange format file, the sub-route addresses of each sub-application are obtained based on their respective data exchange format files. Then, by calling the route merging method in the parent application's data exchange format file, the sub-route addresses of each sub-application and the root route address of the parent application are merged to obtain the target route address. This further improves the method of generating the target route address. The route pages of each sub-application can be arbitrarily combined according to business scenarios, and page loading does not incur additional overhead.

[0072] Example 3

[0073] Figure 3 This is a flowchart of a sub-application page loading method provided in Embodiment 3 of the present invention. This embodiment provides a preferred example based on the above embodiments.

[0074] like Figure 3 As shown, the method includes the following specific steps:

[0075] S310. In response to a user's request to access the business functions of a business project, load the hypertext markup file of the parent application of the business project according to the project resource address of the business project.

[0076] S320. Identify at least one sub-application associated with the business function using pre-configured environment parameters in a hypertext markup file.

[0077] The configuration method for the environmental parameters is as follows:

[0078] Identify at least one business function of the business project and determine the sub-applications associated with each business function; generate the function-application mapping relationship between each business function and the corresponding sub-application; configure the environment parameters according to the function-application mapping relationship and the application configuration parameters related to each sub-application.

[0079] S330: Load the data exchange format file of the parent application via the hypertext markup file.

[0080] The parent application's hypertext markup file may include at least one placeholder; the placeholder is used to represent different environmental parameters corresponding to different business projects.

[0081] S340. Parse the data exchange format file of the parent application. During the parsing process, the asynchronous loader is called through the pre-configured page rendering method to obtain and load the data exchange format file of the sub-application corresponding to the application version number from the static server based on the application version number of each sub-application.

[0082] S350. By calling the route acquisition method in the data exchange format file of the parent application, the sub-route address of each sub-application is obtained based on the data exchange format file of each sub-application.

[0083] S360: By calling the route merging method in the data exchange format file of the parent application, the sub-route addresses of each sub-application and the root route address of the parent application are merged to obtain the target route address, so that users can access the pages of the sub-applications associated with the business functions based on the target route address.

[0084] Example 4

[0085] Figure 4 This is a schematic diagram of a sub-application page loading device provided in Embodiment 4 of the present invention. The sub-application page loading device provided in this embodiment of the present invention is applicable to loading pages of sub-applications associated with the business functions of a business project. This sub-application page loading device can be implemented in hardware and / or software, such as... Figure 4 As shown, the device specifically includes: a hypertext file loading module 401, a sub-application determination module 402, a format file determination module 403, and a target route generation module 404. Among them,

[0086] The hypertext file loading module 401 is used to respond to a user's access request for the business functions of a business project and load the hypertext markup file of the parent application of the business project according to the project resource address of the business project.

[0087] The sub-application determination module 402 is used to determine at least one sub-application associated with the business function through pre-configured environment parameters in the hypertext markup file;

[0088] The format file determination module 403 is used to load the data exchange format files of each of the sub-applications through the hypertext markup file;

[0089] The target route generation module 404 is used to generate a target route address based on the data exchange format file of each of the sub-applications, so that the user can access the sub-applications associated with the business function based on the target route address.

[0090] This invention's technical solution responds to a user's access request for a business function of a business project by loading the hypertext markup file of the parent application of the business project based on the project resource address; determining at least one sub-application associated with the business function through pre-configured environment parameters in the hypertext markup file; loading the data exchange format files of each sub-application through the hypertext markup file; and generating a target routing address based on the data exchange format files of each sub-application, allowing the user to access the page of the sub-application associated with the business function based on the target routing address. This technical solution determines and loads the corresponding sub-applications by loading pre-configured environment parameters, and configures the sub-applications to be loaded under different environment functions as needed. This achieves flexible combination of sub-application pages for different business functions, thereby improving the loading efficiency of pages associated with business functions and avoiding the additional loading time overhead caused by switching between sub-application pages. By merging sub-application routes, the routes of sub-applications are combined into the actual routes required by the business function. When a user accesses a business function of a business project through a browser, the experience of switching between different sub-application pages is the same as switching within the same sub-application, with no additional overhead, smooth interaction, and improved user experience.

[0091] Optionally, the format file determination module 403 includes:

[0092] A format file loading unit is used to load the data exchange format file of the parent application through the hypertext markup file;

[0093] The format file parsing unit is used to parse the data exchange format file of the parent application and, during the file parsing process, call a pre-configured page rendering method to load the data exchange format files of each of the sub-applications.

[0094] Optionally, the format file parsing unit is specifically used for:

[0095] During the file parsing process, the pre-configured page rendering method calls the asynchronous loader to obtain and load the data exchange format file corresponding to the application version number of each sub-application from the static server.

[0096] Optionally, the target route generation module 404 includes:

[0097] The sub-route address acquisition unit is used to acquire the sub-route address of each sub-application based on the data exchange format file of each sub-application by calling the route acquisition method in the data exchange format file of the parent application.

[0098] The target route generation unit is used to merge the sub-route addresses of each sub-application and the root route address of the parent application by calling the route merging method in the data exchange format file of the parent application to obtain the target route address.

[0099] Optionally, the environmental parameters can be configured as follows:

[0100] Identify at least one business function of a business project, and identify the sub-applications associated with each of the business functions;

[0101] Generate the functional application mapping relationship between each of the aforementioned business functions and the corresponding sub-applications;

[0102] Configure the environment parameters according to the functional application mapping relationship and the application configuration parameters related to each sub-application.

[0103] Optionally, the hypertext markup file of the parent application includes at least one placeholder; the placeholder is used to represent different environmental parameters corresponding to different business projects.

[0104] The sub-application page loading device provided in this embodiment of the invention can execute the sub-application page loading method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0105] Example 5

[0106] Figure 5 A schematic diagram of an electronic device 50 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0107] like Figure 5As shown, the electronic device 50 includes at least one processor 51 and a memory, such as a read-only memory (ROM) 52 and a random access memory (RAM) 53, communicatively connected to the at least one processor 51. The memory stores computer programs executable by the at least one processor. The processor 51 can perform various appropriate actions and processes based on the computer program stored in the ROM 52 or loaded into the RAM 53 from storage unit 58. The RAM 53 can also store various programs and data required for the operation of the electronic device 50. The processor 51, ROM 52, and RAM 53 are interconnected via a bus 54. An input / output (I / O) interface 55 is also connected to the bus 54.

[0108] Multiple components in electronic device 50 are connected to I / O interface 55, including: input unit 56, such as keyboard, mouse, etc.; output unit 57, such as various types of monitors, speakers, etc.; storage unit 58, such as disk, optical disk, etc.; and communication unit 59, such as network card, modem, wireless transceiver, etc. Communication unit 59 allows electronic device 50 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0109] Processor 51 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 51 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 51 performs the various methods and processes described above, such as the sub-application page loading method.

[0110] In some embodiments, the sub-application page loading method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 58. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 50 via ROM 52 and / or communication unit 59. When the computer program is loaded into RAM 53 and executed by processor 51, one or more steps of the sub-application page loading method described above may be performed. Alternatively, in other embodiments, processor 51 may be configured to execute the sub-application page loading method by any other suitable means (e.g., by means of firmware).

[0111] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0112] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0113] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0114] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0115] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0116] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0117] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and no limitation is imposed herein.

[0118] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for loading a sub-application page, characterized in that, include: In response to a user's request to access the business functions of a business project, the hypertext markup file of the parent application of the business project is loaded according to the project resource address of the business project. At least one sub-application associated with the business function is determined by using pre-configured environment parameters in the hypertext markup file; The data exchange format files of each of the sub-applications are loaded using the hypertext markup file; By calling the route acquisition method in the data exchange format file of the parent application, the sub-route address of each sub-application is obtained based on the data exchange format file of each sub-application; By calling the route merging method in the data exchange format file of the parent application, the sub-route addresses of each sub-application and the root route address of the parent application are merged to obtain the target route address, so that the user can access the page of the sub-application associated with the business function based on the target route address.

2. The method according to claim 1, characterized in that, The step of loading the data exchange format files of each of the sub-applications through the hypertext markup file includes: The data exchange format file of the parent application is loaded through the hypertext markup file; The data exchange format file of the parent application is parsed, and during the parsing process, a pre-configured page rendering method is called to load the data exchange format files of each of the sub-applications.

3. The method according to claim 2, characterized in that, The process of calling a pre-configured page rendering method to load the data exchange format files of each sub-application during file parsing includes: During the file parsing process, the pre-configured page rendering method calls the asynchronous loader to obtain and load the data exchange format file corresponding to the application version number of each sub-application from the static server.

4. The method according to claim 1, characterized in that, The configuration method for the environmental parameters is as follows: Identify at least one business function of a business project, and identify the sub-applications associated with each of the business functions; Generate the functional application mapping relationship between each of the aforementioned business functions and the corresponding sub-applications; Configure the environment parameters according to the functional application mapping relationship and the application configuration parameters related to each sub-application.

5. The method according to claim 1, characterized in that, in, The hypertext markup file of the parent application includes at least one placeholder; the placeholder is used to represent different environmental parameters corresponding to different business projects.

6. A sub-application page loading device, characterized in that, include: The hypertext file loading module is used to respond to a user's access request for the business functions of a business project, and load the hypertext markup file of the parent application of the business project according to the project resource address of the business project. The sub-application determination module is used to determine at least one sub-application associated with the business function by using pre-configured environment parameters in the hypertext markup file. The format file determination module is used to load the data exchange format files of each of the sub-applications through the hypertext markup file; The target route generation module is used to obtain the sub-route address of each sub-application based on the data exchange format file of each sub-application by calling the route acquisition method in the data exchange format file of the parent application; and to merge the sub-route address of each sub-application with the root route address of the parent application by calling the route merging method in the data exchange format file of the parent application to obtain the target route address, so that the user can access the page of the sub-application associated with the business function based on the target route address.

7. The apparatus according to claim 6, characterized in that, The format file determination module includes: A format file loading unit is used to load the data exchange format file of the parent application through the hypertext markup file; The format file parsing unit is used to parse the data exchange format file of the parent application and, during the file parsing process, call a pre-configured page rendering method to load the data exchange format files of each of the sub-applications.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the sub-application page loading method according to any one of claims 1-5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the sub-application page loading method according to any one of claims 1-5.

Images