CN116541621A

CN116541621A - Page rendering method and device

Info

Publication number: CN116541621A
Application number: CN202310374187.0A
Authority: CN
Inventors: 王志坚; 秦丹涛; 胡堃
Original assignee: Shenzhen Huawei Cloud Computing Technology Co ltd
Current assignee: Shenzhen Huawei Cloud Computing Technology Co ltd
Priority date: 2023-03-29
Filing date: 2023-03-29
Publication date: 2023-08-04

Abstract

A page rendering method and device. The method comprises the following steps: the browser determines a routing address of a second application based on a triggering operation of a link of the user to the second application on a page of the first application, and sends the routing address to the Web application framework, wherein the second application is a sub-application of the first application, and the first application is a main application of the second application. The framework receives a first routing address, wherein the first routing address is a routing address of a second application; intercepting a first routing address and a second routing address through a sandbox, and generating a third routing address according to the first routing address and the second routing address, wherein the second routing address is a routing address corresponding to a page of the first application; and then, according to the third routing address, acquiring page resources of the second application, and rendering the page of the second application. The method and the device realize that the routing conflict between the main application and the sub-application is prevented in the frame layer, further prevent that the page of the sub-application cannot be rendered or the page data after rendering is inaccurate, and ensure the page rendering accuracy of the sub-application.

Description

Page rendering method and device

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for rendering a page.

Background

The page integration system based on the micro front end comprises a plurality of independent Web applications, and each Web application can be rendered by a SPA (single page Web application, single page application) page. The SPA page is integrated by a main application and a sub application, wherein the main application is a service unit loaded firstly when the SPA page is formed, the sub application is a service unit loaded in the main application, has independent routing addresses, contains complete service realization and can be independently rendered, and one sub application can be integrated by a plurality of different main applications.

When one sub-application of the page integration system is accessed, if the sub-application cannot know which main application is integrated, a route conflict situation exists between the sub-application and the main application, so that the page resource of the sub-application cannot be acquired, and the page of the sub-application cannot be rendered. Therefore, how to solve the routing conflict between the sub-application and the main application and avoid the problem that the page cannot be accurately rendered due to the routing conflict is a technical problem to be solved at present.

Disclosure of Invention

The embodiment of the application provides a page rendering method and device, which are used for avoiding route conflict between a sub-application and a main application and ensuring the accuracy of page rendering of the sub-application.

In a first aspect, an embodiment of the present application proposes a page rendering method, where the method is applied to a Web application framework. The method comprises the following steps: the method comprises the steps that a Web application framework receives a first routing address, wherein the first routing address is sent by a browser in response to user operation, the user operation is used for triggering a second application on a page of a first application, the second application is a sub-application of the first application, and the first routing address is a routing address of the second application; generating a third routing address according to the first routing address and a second routing address, wherein the second routing address is a routing address corresponding to a page of the first application; acquiring page resources of the second application according to the third routing address; and rendering the page of the second application according to the page resource of the second application.

Based on the scheme, the Web application framework comprises a resource loading unit and a sandbox unit; the first application and the second application may be Web applications, i.e. the first application is a first Web application and the second application is a second Web application. After rendering the page of the first Web application, the user can trigger the link of the second Web application on the page of the first Web application, and the browser determines the routing address of the second Web application through the link of the second Web application and sends the routing address of the second Web application to the Web application framework. The routing address corresponding to the second Web application does not comprise the routing address corresponding to the first Web application.

After receiving the routing address corresponding to the first Web application, the Web application framework intercepts the routing of the second Web application through the sandbox unit, then generates a third routing address according to the routing address corresponding to the first Web application and the routing address corresponding to the second Web application, further obtains the page resource of the second Web application according to the third routing address instead of obtaining the page resource of the second Web application according to the routing address corresponding to the second Web application, and is equivalent to determining the main application integrated by the sub-application, so that the routing change of the sub-application is prevented from influencing the routing of the main application, the routing conflict between the main application and the sub-application is prevented in the framework layer, the situation that the page of the sub-application cannot be rendered or the page data after rendering is inaccurate is prevented, and the page rendering accuracy of the sub-application is ensured.

In some embodiments, the third routing address includes a domain name of the first routing address and a prefix, the prefix being the second routing address.

Based on the scheme, the Web application framework generates the third routing address by adding the domain name of the routing address corresponding to the second Web application after the routing address corresponding to the first Web application, so that the third routing address can not only indicate that the main application integrated by the second Web application is the first Web application, but also realize that the main application is routed to the second Web application according to the third routing address, and the page resource acquisition and rendering of the second Web application are not influenced while the routing conflict between the main application and the sub-application is prevented.

In some embodiments, further comprising: and the Web application framework sends the third routing address to the browser so that the browser displays the third routing address in an address bar of the browser.

Based on the scheme, when the browser renders the page of the second Web application, the third routing address is displayed in the address bar of the browser, the main application integrated by the second Web application is embodied, and the integrity of the routing address in the page of the second Web application is ensured.

In some embodiments, prior to receiving the first routing address, the Web application framework further determines tool library resources on which at least two sub-applications of the first application depend, the at least two sub-applications including the second application; determining a common tool library resource on which the at least two sub-applications depend, the common tool library resource being an intersection of the at least two sub-application dependent tool library resources; and loading the public tool library resource.

Based on the scheme, before acquiring the page resources of the sub-application of the first Web application, the Web application framework determines tool library resources (such as a real library, a load library and a movement library) on which at least two sub-applications depend through a scanning tool (such as a cli tool), then determines and loads common tool library resources on which at least two sub-applications depend, so that repeated acquisition of the tool library resources during loading of different sub-applications is avoided, the data volume of acquiring the page resources of the sub-applications is reduced, the time for acquiring the page resources of the sub-applications is reduced, and the page rendering efficiency of the sub-applications is improved.

In some embodiments, after receiving the first routing address, the Web application framework further loads a first tool library resource on which the second application depends, the first tool library resource being a tool library resource other than the common tool library resource in the second application-dependent tool library resource.

Based on the above scheme, the tool library resources are used for data processing, and in order to ensure the accuracy of page rendering of the second Web application, the Web application framework also needs to load all tool library resources on which the second Web application depends, namely, the common tool library resources and the first tool library resources.

In some embodiments, prior to receiving the first routing address, the Web application framework further determines a third application on which the second application depends, the third application being a child of the first application; loading first information; the first information is service information used by the second application and the third application.

Based on the scheme, before the user triggers the link of the second Web application, the Web application framework preloads the service information required by the second Web application, so that the forced loading sequence between the second Web application and the third Web application is relieved, and the complexity of sub-application control is reduced. And after the user triggers the link of the second Web application, the page resource of the second application is not required to be acquired after the business data of the third Web application is loaded, so that the waiting time of the business information required by the second Web application is avoided, the time for acquiring the page resource of the second Web application is reduced, and the page rendering efficiency is improved.

In some embodiments, according to the third routing address, acquiring the page resource of the second application, including the Web application framework acquiring the first data from the network side according to the third routing address; passing the first data and the first information to the second application; and acquiring the page resource generated by the second application according to the first data and the first information.

Based on the scheme, after the first data and the first information are acquired, the Web application framework transmits the first data and the first information to the second Web application, and the second Web application processes the first data and the first information, so that the second Web application is ensured to independently operate, and the technical stack coupling between the second Web application and other sub-applications is avoided.

In some embodiments, after rendering the page of the second application, the Web application framework further obtains page resources of a fourth application, the fourth application being a child application of the second application; and when the link of the fourth application on the page of the second application is triggered, rendering the page of the fourth application according to the page resource of the fourth application.

Based on the scheme, the fourth Web application depends on the page of the second Web application, and the page resource of the fourth application is preloaded, so that after the user triggers the link of the fourth Web application on the page of the second Web application, the page of the fourth application is directly rendered according to the page resource of the fourth application, the page rendering time is reduced, and the page rendering efficiency is improved.

In a second aspect, an embodiment of the present application proposes an apparatus, including a receiving unit and a processing unit; the receiving unit is used for receiving a first routing address, the first routing address is sent by the browser in response to user operation, the user operation is used for triggering a second application on a page of a first application, the second application is a sub-application of the first application, and the first routing address is a routing address of the second application; the processing unit is used for generating a third routing address according to the first routing address and a second routing address, wherein the second routing address is a routing address corresponding to a page of the first application; acquiring page resources of the second application according to the third routing address; and rendering the page of the second application according to the page resource of the second application.

In some embodiments, the processing unit is further to: and sending the third routing address to the browser so that the browser displays the third routing address in an address bar of the browser.

In some embodiments, the processing unit is further to: before receiving a first routing address, determining tool library resources on which at least two sub-applications of the first application depend, wherein the at least two sub-applications comprise the second application; determining a common tool library resource on which the at least two sub-applications depend, the common tool library resource being an intersection of the at least two sub-application dependent tool library resources; and loading the public tool library resource.

In some embodiments, the processing unit is further to: after receiving the first routing address, loading a first tool library resource on which the second application depends, wherein the first tool library resource is a tool library resource except the public tool library resource in the tool library resources on which the second application depends.

In some embodiments, the processing unit is further to: before receiving a first routing address, determining a third application on which the second application depends, wherein the third application is a sub-application of the first application; loading first information; the first information is service information used by the second application and the third application.

In some embodiments, the processing unit is specifically configured to: acquiring first data from a network side according to the third routing address; passing the first data and the first information to the second application; and acquiring the page resource generated by the second application according to the first data and the first information.

In some embodiments, the processing unit is further to: after rendering the page of the second application, acquiring page resources of a fourth application, wherein the fourth application is a sub-application of the second application; and when the link of the fourth application on the page of the second application is triggered, rendering the page of the fourth application according to the page resource of the fourth application.

In a third aspect, embodiments of the present application provide a readable storage medium storing a program comprising program code which, when run on a device, causes the device to perform the method of the first aspect described above.

In a fourth aspect, embodiments of the present application provide an apparatus, including: one or more processors; wherein the instructions of the one or more computer programs, when executed by the one or more processors, cause the apparatus to perform the method as described above in the first aspect.

In a fifth aspect, embodiments of the present application provide a chip system, including at least one chip and a memory, where the at least one chip is coupled to the memory, and configured to read and execute program instructions stored in the memory, so as to implement the method described in the first aspect.

In a sixth aspect, embodiments of the present application provide a computer program product, which when run on a computer causes the computer to perform the method of the first aspect described above.

Further combinations of embodiments of the present application may be made to provide further implementations based on the implementations provided in the above aspects.

The technical effects achievable in any one of the second to sixth aspects described above may be correspondingly described with reference to the technical effects achievable in the first aspect described above, and the descriptions will be omitted.

Drawings

Fig. 1 is a schematic architecture diagram of a page integration development framework according to an embodiment of the present application;

fig. 2 is a schematic diagram of a hierarchical software structure of a terminal device according to an embodiment of the present application;

fig. 3 is a flow chart of a page rendering method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a sub-application loading tool library resource according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a page rendering device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a page rendering device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include, for example, "one or more" such forms of expression, unless the context clearly indicates to the contrary. It should also be understood that in embodiments of the present application, "one or more" means one, two, or more than two; "and/or", describes an association relationship of the association object, indicating that three relationships may exist; for example, a and/or B may represent: a alone, a and B together, and B alone, wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

The plurality of the embodiments of the present application refers to greater than or equal to two. It should be noted that, in the description of the embodiments of the present application, the terms "first," "second," and the like are used for distinguishing between the descriptions and not necessarily for indicating or implying a relative importance, or alternatively, for indicating or implying a sequential order.

In order to better explain the technical solution of the present application, the terms appearing in the embodiments of the present application are explained below.

Web (World Wide Web or Wide area network): is a network service established on the Internet, and provides graphical and easily accessible Web pages for users to search and browse information on the Internet.

HTML (Hyper Text Markup Language ): the content of the Web page is information which is put on the Web page and is intended to be browsed by a user, and can contain characters, pictures, videos and the like.

CSS (Cascading Style Sheets, cascading style sheet): the visual appearance of the Web page is described, and the visual appearance comprises a title font, a color change, a background picture added to the title, a border and the like.

JS (JavaScript): the method is used for realizing the special effect of the Web page, and the special effect comprises the following steps: the mouse slides over a pop-up drop-down menu, the mouse slides over a background color change of the form, rotation of information, etc.

SPA (Single Page Application ): a single page Web application refers to setting all functions of the Web application in one Web page, and loading corresponding HTML, javascript, and CSS only when the Web page is initialized. Once the loading of the Web page is completed, the SPA does not reload or jump the Web page due to the operation of the user, but instead, the JavaScript is utilized to dynamically transform the content of the HTML, so that the interaction between the Web application and the user is realized.

Sandbox (Sandbox): is a virtual system program that allows a browser or other program to be run in a sandbox environment, changes made by the run can be subsequently deleted, and the program running inside it cannot permanently affect the hard disk. Sandboxes refer to systems used in isolated environments to shield an operating program in the sandboxed environment from access to external objects.

And (3) routing: in the embodiment of the application, the process that the browser routes to the corresponding page through the change of the routing address is shown.

Web application framework: for supporting the development of dynamic websites, web applications, and web services. For convenience of description, the embodiment of the present application is simply referred to as a frame.

With the rapid development of cloud computing, a micro-service development mode gradually extends from a service end field to a front end field. A micro-service, among other things, can be understood as a variant of a service-oriented architecture style, which divides a single application into a small set of services that coordinate and interwork with each other. Under the development mode of single-page Web application, the business is accumulated and accumulated day by day, new business is continuously online, and the single-page Web application gradually grows into a boulder application, so that the reconstruction and modification of the single-page Web application are difficult and the complexity is high. In the scene of service multiplexing, application integration or integrated, the components generally only contain view logic and do not contain service logic, so that the multiplexing of the components cannot meet the requirements. Therefore, the page construction mode of the micro front end is generated.

Micro front-end is a front-end development mode similar to back-end micro services, and front-end development can be understood as a process of creating a front-end interface such as a Web page or APP (application program) to be presented to a user. In a page integration scenario, a page of a main application is generated by integrating multiple different sub-applications into the same Web page, where a sub-application may also be referred to as a page block, is the smallest business unit in the Web page composition, contains complete business implementation (including view logic and business logic), and may be rendered independently, and one sub-application may be integrated by multiple different main applications. In the micro-front end page integration development framework, the business units that the incoming framework first loads are called host applications, or page bodies. For example, the framework includes a sub-application 1, a sub-application 2 and a sub-application 3, where the sub-application 1 and the sub-application 2 are integrated into a main application a, and the sub-application 1 may be integrated with the sub-application 3 into a main application B. When the user triggers the main application A in the browser on the terminal equipment, the browser can route the Web pages containing a plurality of main applications to the Web pages of the main application A through the change of the route, namely, the switching of different SPAs is completed through the route, so that the switching among the Web applications can not trigger the reloading of the Web pages. Therefore, each sub-application is independently developed, constructed and deployed, and when the main application associated with the service requirement is reconstructed or modified according to different service requirements, for example, integrated sub-applications are added, deleted and/or modified in the main application, the reconstruction and modification difficulties and the modification complexity of the Web page are reduced.

However, in the page integration system constructed based on the micro front end, when a sub-application on the page of the main application is accessed, if the sub-application cannot know which main application is integrated, the routing address fed back to the page integration system may only include the routing address of the sub-application and not include the access path of the main application, so that the display interface of the device deployed with the page integration system only displays the content of the sub-application, does not display the content corresponding to the main application, or fails to display the content, and the sub-application and the main application have a routing conflict. For example, when the user triggers the sub-application 1, the browser may not determine which main application corresponding to the sub-application 1 is, so that a newly rendered page after the user triggers the sub-application 1 cannot be accurately displayed.

Therefore, the embodiment of the application provides a page rendering method, by which the route of the sub-application is isolated, and when the sub-application is routed, the page resource of the sub-application is acquired according to the newly generated route address, so that the route conflict between the sub-application and the main application is solved, and the problem that the page cannot be accurately rendered due to the route conflict is avoided.

Embodiments of the present application are described in detail below with reference to the accompanying drawings.

First, a system architecture of an embodiment of the present application will be described. Referring to fig. 1, an architecture diagram of a page integration development framework to which a page rendering method provided in an embodiment of the present application is applicable includes a scanning module 110, a resource loading module 120, a message bus module 130, a status management module 140, a JS sandbox module 150X, CSS sandbox module 150Y, a routing sandbox module 150Z, a public dependency module 160, a menu module 170, an application registration module 180, and a cross-domain security module 190.

A scanning module 110 for providing management functions for the common dependent resources of the sub-applications. The scan module 110 includes one or more tools, such as the scan module 110 is to include a cli tool. The cli tool is a development supporting tool provided by a framework and is used for realizing packaging of applications. For example, in a packing scene, the tool is presented as a plug-in, and when the packing action is executed, the plug-in is loaded, and the plug-in can scan out all modules on which the current service depends and register the modules on a dependence center, and the dependence center can acquire information such as the name, the dependence list, the dependent version and the like of the service. In the embodiment of the application, the c li tool can scan the tool library resources on which at least two sub-applications depend, intercept the packaging process of the at least two sub-applications in the construction process of the sub-applications, determine the common tool library resources of the at least two sub-applications, and strip the common tool library resources from the construction output.

The resource loading module 120 may provide loading control of resources required by the sub-application, where the resources required by the sub-application include tool library resources, business data, and page resources.

A message bus module 130, configured to implement message passing between at least two sub-applications, such as passing service information of two sub-applications having a dependency relationship. Optionally, the message bus module 130 is an asynchronous message bus, and may provide the needed resource for preloading the sub-application before the link of the sub-application is triggered by the user, so as to reduce the process of waiting for the network request during page rendering, and improve the efficiency of page rendering. Optionally, the asynchronous message bus includes a message buffer function, so that state information of the sub-applications can be buffered, and thus, time sequence problems of monitoring service messages and sending the service messages do not need to be concerned between the sub-applications, and loading sequences of the sub-applications do not need to be concerned, and control complexity of the sub-applications is reduced.

The state management module 140 is configured to determine state information of the sub-application through an interface for accessing the sub-application, and manage the state information of the sub-application, such as a loading order of the sub-application and a state of a resource required for loading.

The JS sandbox module 150X is configured to isolate global variables and events of the sub-applications, and ensure that global variables or events between at least two sub-applications do not conflict. The page behavior of the sub-application and the interaction between the user and the page of the sub-application are operated in a single environment, and the operation of other sub-applications outside the environment is not influenced.

The CSS sandbox module 150Y is configured to perform isolation control on the presentation style of the content of the sub-application, that is, the presentation style of the content of each sub-application is separately run in a separate environment, so as to avoid style pollution.

The routing sandbox module 150Z is configured to isolate the routing behavior of the sub-application, and prevent routing conflicts between the sub-application and the main application, that is, the routing process of each sub-application and the routing process of the main application operate in different environments, so as to avoid the situation that the sub-application cannot be loaded accurately.

A common dependency module 160 for storing common tool library resources of at least two sub-applications.

The menu module 170 is a menu UI (user interface) of the user integrated page, and is used for providing links of each sub-application, wherein the links of the sub-application include text, icons, pictures, and the like. For example, icons corresponding to the sub-applications are displayed in the menu UI, and the user triggers the links of the sub-applications by clicking the icons corresponding to the sub-applications.

The application registration module 180 is configured to provide a function of registering each sub-application and a page link included in each sub-application.

The cross-domain security module 190 is configured to implement cross-system access to the sub-applications and resource authentication of the sub-applications, for example, the sub-applications of different service systems are accessed through the cross-domain security module 190, where the main application is different from the service system of the sub-applications. Alternatively, the cross-domain security module 190 may be a Proxy agent module.

In one possible implementation, the framework shown in fig. 1 is applied in a software system of a terminal device. Optionally, the terminal device may be a mobile phone, a tablet computer, a notebook computer, a netbook, a vehicle-mounted device, a business intelligent terminal (including a video phone, a conference desktop intelligent terminal, etc.), a personal digital assistant (personal digital assistant, PD a), an augmented reality (augmented reality, AR) \virtual reality (VR) device, etc., which is not limited to the specific form of the terminal device in the embodiment of the present application.

The software system of the terminal device can adopt a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture or a cloud architecture. Embodiments of the present application provide software systems (e.g., android) in a hierarchical architecture System) is an example, a software structure of the terminal device is exemplified. Referring to fig. 2, a schematic hierarchical software structure of a terminal device according to an embodiment of the present application is provided. The layered architecture divides the software system of the terminal device into several layers, each layer having a respective role and division. Layer-to-layer through software interfaceAnd (5) communication. The Android system is divided into four layers, namely an application layer (applications) 210, an application framework layer (application framework) 220, an Android running environment ART (Android runtime), a system library and a kernel layer (kernel), and the embodiment of the application does not limit layering of a software structure of the terminal device. An Zhuoyun row and system libraries and kernel layers may be considered a layer, referred to as system layer 230. It should be understood that fig. 2 further adds a hardware layer 240 in the terminal device based on the Android system.

It should be understood that the modules included in the respective layers shown in fig. 2 are modules involved in the embodiments of the present application, and the modules included in the respective layers below do not constitute limitations on the structure of the terminal device and the hierarchy (illustration) of the module deployment. The modules shown in fig. 2 may be deployed alone or several modules may be deployed together, with the division of modules and the names of modules in fig. 2 being merely one example.

The application layer may include a series of application packages. The application layer may include camera, gallery, calendar, conversation, map, navigation, bluetooth, music, video, short message, browser, etc. applications. The application programs may include system applications and third party applications. Only the first application 211 and the second application 212 are shown by way of example. Illustratively, the first application 211 may be a game-like application and the second application 212 may be a browser. The browser is software which can be installed on the terminal equipment, and the browser provided by the embodiment of the application has the functions of rendering pages and accessing application programs of different systems.

The application framework layer may provide an application programming interface (application program ming interface, API) and programming framework for application programs of the application layer. The application framework layer may include some predefined functions. Referring to fig. 2, the application framework layer includes all the modules shown in fig. 1, such as the resource loading module 120, the message bus module 130, the routing sandbox module 150Z and the like shown in fig. 1, and the functions of each module are not described herein. The application framework layer also includes other modules such as a window management service (window manager service, WMS) module, a graphical image processing module, and the like. The window management service module is used for managing the user interface, and the graphic image processing module is used for drawing the user interface. The graphic image processing module may include a rendering module for rendering the user interface according to the page resource and a layer synthesizer for synthesizing the rendered layers to obtain the user interface to be displayed.

Because An Zhuoyun rows and system libraries and kernel layer are considered a layer in the present embodiment, an Zhuoyun rows and system libraries and functional modules in kernel layer may be included in system layer 230. Referring to fig. 2, the system layer may include a driver of hardware for driving the hardware to operate. For example: a display driver (231), a sensor driver 232, a graphics processor driver (graphics processing unit driver, GPU driver) 233, and the like, to which the embodiments of the present application are not limited.

The hardware layer 240 includes hardware in the terminal device. It will be appreciated that the hardware layers in fig. 2 show a display 241, a sensor 242, etc. involved in the embodiments described below.

Based on the architecture schematic diagram of the framework shown in fig. 1, the framework is used for isolating the routing of the sub-application, and when the sub-application is routed, the page resources of the sub-application are obtained according to the newly generated routing address, referring to fig. 3, fig. 3 is a schematic flow diagram of a page rendering method provided by an embodiment of the present application, where the flow specifically includes:

in step 310, the browser renders a page of the first Web application in response to a first operation by the user.

The first Web application is an exemplary main application, the first operation of the user indicates that the user triggers the link of the first We b application on the browser, and the link of the first Web application can be displayed on the page of the browser in an icon mode. For example, the page of the browser includes icons corresponding to links of the main application a, the main application B and the main application C, and the first operation of the user is to click the icon corresponding to the link of the main application a, so as to trigger the link of the main application a. After the link of the main application a is triggered, the browser responds to the first operation of the user, acquires the page resource of the main application a according to the link (or link address, such as uniform resource identifier (Uniform Resource Identifier, URI)) of the main application a, and renders the page of the main application a. The page resource may include HTML, CSS, JS information, etc.

In one possible implementation manner, after the browser renders the page of the main application, at least one sub-application is selected from the main application according to the set preloading rule, and the first information of the sub-application is preloaded. The first information is service information that the sub-application needs to use, for example, the first information is identity information, a user name, a telephone number, a password, and the like of the user. The first information may also be referred to as dependency state information. The preloading rules may be determined according to the historical trigger times of all sub-applications of the main application, and optionally, the first information of the sub-applications with more trigger times or higher trigger frequency may be preloaded. For example, the main application a includes a sub-application 1, a sub-application 2 and a sub-application 3, in historical data of one month in history, the number of times of triggering the sub-application 1 by a user is 10, the number of times of triggering the sub-application 2 by the user is 8, and the number of times of triggering the sub-application 3 by the user is 7, and the sub-application 1 is regarded as a preloaded sub-application.

For example, it is possible that other sub-applications may be nested in each sub-application, i.e., there is a nested dependency between at least two sub-applications. For this case, the process of preloading the first information may be: the method comprises the steps of determining the sub-application with the dependency relationship in the main application according to interface information by scanning interface information of all sub-applications in the main application, and preloading first information of the sub-application with the dependency relationship, wherein the first information is service information required to be used by the sub-application with the dependency relationship, and can also be called as public state information of the sub-application with the dependency relationship. For example, in the first Web application, the second Web application and the third Web application are sub-applications of the first Web application, and the second Web application depends on the third Web application, and assuming that the third Web application and the second Web application both require a user name and a password (i.e., the user name and the password are first information of the third wieb application and the second Web application, which may also be referred to as common state information of the third Web application and the second Web application), the user name and the password of the user are preloaded. Alternatively, the preloaded first information may be stored to the message bus module 130 shown in fig. 1.

In the related art, since the second Web application depends on the third Web application, when acquiring the page resources of the second Web application, it is required to monitor the message of the loading state of the page resources of the third Web application, after the loading of the page resources of the third Web application is completed, receive the first information sent by the third Web application, and acquire the page resources of the second Web application. In the embodiment of the present application, the first information that needs to be used by the preloaded third Web application and the second Web application is cached by the message bus module 130, when the page resource of the second Web application is acquired, the cached first information can be directly acquired from the message bus module 130, without waiting for the completion of the loading of the page resource of the third Web application, the page resource of the second We b application can be acquired first, and then the page resource of the third Web application is acquired, so that the sub-application is realized without monitoring the message, without concern about the loading time sequence problem between the sub-applications, the forced loading sequence of the sub-application with a dependency relationship is released, and the complexity of the sub-application control is reduced.

In another possible implementation manner, after the browser renders the page of the main application, the common tool library resources of at least two sub-applications corresponding to the main application are preloaded. The tool library can also be called library functions, including a reaction library, a lodas h library, a movement library and the like, and has a data processing function. A common tool library resource is an intersection of at least two sub-application dependent tool library resources.

Illustratively, the process of preloading the common tool library resources may be: by scanning interface information of all sub-applications in the main application, determining tool library resources relied by all sub-applications according to the interface information, then determining public tool library resources relied by at least two sub-applications, and preloading the public tool library resources. Alternatively, preloaded common tool library resources may be cached to common dependency module 160. For example, the tool library resources relied by the sub-application 1 include a react library and a lodash library, the tool library resources relied by the sub-application 2 include a react library and a move library, and then the react library is used as a public tool library resource of the sub-application 1 and the sub-application 2, and the react library is cached in the public relying module 160.

Because the public tool library resources are preloaded, when the tool library resources relied by the sub-application are loaded, the cached preloaded public tool library resources can be directly obtained from the public relying module 160, the public tool library resources are not required to be loaded, the resource loading amount is saved, repeated obtaining of the tool library resources when pages of different sub-applications are rendered is avoided, the data amount of obtaining the page resources of the sub-application is reduced, the time delay of obtaining the page resources of the sub-application is reduced, and the page rendering efficiency of the sub-application is improved.

In step 320, the browser determines a routing address for the second Web application in response to the second operation by the user.

The second Web application is an application of the first Web application, the link of the first Web application is displayed on the page of the first Web application, and the user triggers a second operation for the second Web application on the page of the first Web application, thereby triggering the link of the second Web application. After determining that the link of the second Web application is triggered, the browser routes the second We b application to obtain a routing address of the second Web application (for convenience of description, the routing address of the second Web application is referred to as a first routing address hereinafter), where the routing address may be a URL (uniform resource locator ) address.

In step 330, the browser sends the routing address of the second Web application.

After obtaining the first routing address, the browser sends the first routing address to the framework (the framework is as described above in fig. 1) so that the framework obtains the page resource of the second Web application based on the first routing address.

In step 340, the framework generates a third routing address based on the routing address of the first Web application (for convenience of description, the routing address of the first Web application will be referred to as a second routing address hereinafter) and the routing address of the second Web application.

Illustratively, after obtaining the second routing address and the first routing address, the framework may isolate the route of the first Web application and the route of the second Web application through the routing sandbox module 150Z shown in fig. 1, intercept the route of the second Web application, and generate the third routing address by adding the domain name of the routing address corresponding to the second Web application to the routing address corresponding to the first Web application. For example, the second routing address is "https: the first routing address is "/sub-application 1/alarm/detail", and the third routing address is "https" by adding the first routing address to the second routing address. Exmample.com/Main application A/sub-application 1/alarm/detail). That is, the third routing address includes a domain name and a prefix of the first routing address, where the prefix is the second routing address, so that it is achieved that the third routing address can not only indicate that the main application integrated by the second Web application is the first Web application (for example, the main application integrated by the sub-application 1 is the main application a), but also can achieve routing of the second Web application according to the third routing address, and when preventing routing conflict between the main application and the sub-application, it does not affect acquisition and rendering of page resources of the second Web application.

When the route is carried out according to the third route address, the main application integrated by the sub-application can be determined, so that the influence of the route change of the sub-application on the route of the main application is avoided, the route conflict between the main application and the sub-application is prevented at the frame layer, the situation that the page of the sub-application cannot be rendered or the page data after rendering is inaccurate is further prevented, and the page rendering accuracy of the sub-application is ensured.

In step 350, the framework obtains the page resource of the second Web application according to the third routing address.

In one possible implementation, when acquiring the page resource of the second Web application, the tool library resource on which the second Web application depends needs to be loaded. In the embodiment of the present application, for convenience of description, tool library resources other than the common tool library resource in the sub-application-dependent tool library resources are referred to as first tool library resources, referring to fig. 4, fig. 4 is a schematic diagram of a sub-application loading tool library resource provided in an example of the present application, based on the above step 310, it can be known that at least two sub-applications in the main application depend on the common tool library resource, and if at least two sub-applications include a second Web application, the loading of the tool library resource on which the second Web application depends first determines whether the second Web application has a dependent common tool library resource, if yes, further determines whether the common tool library resource has been loaded, otherwise, the first tool library resource of the second Web application is directly loaded, where the first tool library resource is all the tool library resources on which the second Web application depends. Optionally, when it is determined that the second Web application has a dependent common tool library resource and the common tool library resource is loaded, loading a first tool library resource of the second Web application, where the first tool library resource is a tool library resource other than the common tool library resource in all tool library resources on which the second Web application depends. For example, the second Web application is sub-application 1, the public tool library resource of sub-application 1 is a reaac t library, and the reaac library is loaded and cached to the public dependency module 160, and the first tool library resource of sub-application 1 is a lodash library, then the reaac library is directly called from the public dependency module 160, and then the lodash library is loaded, so as to obtain all the tool library resources on which the sub-application 1 depends. It is to be understood that the at least two sub-applications may be all sub-applications in the main application, or may be any at least two different sub-applications in the main application, which is not specifically limited herein.

Illustratively, when it is determined that the common tool library resource has been loaded, the common tool library resource cached in the common dependency module 160 is directly invoked without loading the common tool library resource. When the public tool library resources are determined to be not loaded, the public tool library resources are loaded first, and the public tool library resources are cached to the public dependency module 160, so that when pages of other sub-applications are rendered, the public tool library resources do not need to be repeatedly loaded, the resource loading amount is saved, and the page rendering efficiency of the sub-applications is improved.

Based on the above step 310, the first information required to be used by the second Web application may be cached in the message bus module 130 by pre-loading in advance, so that the cached first information may be obtained from the message bus module 130 when the first information is loaded. If the message bus module 130 does not cache the first information, the first information may be obtained after the third Web application that the second Web application depends on loads the first information.

After loading the tool library resource on which the second Web application depends, the framework may call the second Web application to enable the second Web application to acquire the first data from the network side according to the third routing address. The first data may be a static resource such as a FixedPage representing a front end, e.g., HTML, CSS, JS, a picture, etc. data. Optionally, the framework may further transmit the first information to the second Web application, so that the second Web application invokes the tool library resource to perform data processing on the first information and the first data, thereby generating a page resource of the second Web application.

Step 360, the framework renders pages of the second Web application according to the page resources of the second Web application.

Further, after the frame renders the page of the second Web application on the browser, the frame may further send the third routing address to the browser, so that the browser displays the third routing address in an address bar corresponding to the page of the second Web application. By displaying the third routing address in the page of the second Web application, the main application integrated by the second Web application can be embodied, and the integrity of the routing address of the second Web application is ensured.

In a possible implementation manner, after the browser renders the page of the main application based on the step 310, at least one sub-application may be selected from the main application according to the set preloading rule, and the page resource of the sub-application is preloaded. After the link of the sub-application is triggered, the page can be directly rendered according to the preloaded page resources of the sub-application, so that the time delay is reduced. The manner of obtaining the page resources of the sub-application is consistent with the above steps 320 to 350, and will not be described herein. For example, assuming that the second Web application is a selected sub-application capable of resource preloading, before the link of the second Web application is triggered by the user, the page resource of the second Web application is preloaded, after the link of the second Web application is triggered by the user, the page of the second Web application can be directly rendered according to the preloaded page resource of the second Web application, so that time delay of waiting for operations such as network request when the page resource is acquired is saved, the rendering of the sub-application is accelerated, and the rendering efficiency of the sub-application is improved.

Optionally, when at least one sub-application is selected from the main application to perform the preloading of the page resource, the sub-application with more browsing times or more frequent browsing may be selected according to the browsing history of the user.

In yet another possible embodiment, after rendering the page of the second Web application, the framework may further determine a fourth Web application that is dependent on the second Web application, i.e. the fourth Web application is a child application of the second Web application. By preloading page resources on the fourth Web application, when the link of the fourth Web application on the page of the second Web application is triggered, the page of the fourth application is directly rendered according to the preloaded page resources of the fourth application, the page rendering time of the fourth application is reduced, and the page rendering efficiency is improved.

In the embodiment of the application, links of different sub-applications are displayed in a page of any main application, for example, links of different sub-applications are displayed according to the switching of an accordion menu, routes of the main application and the sub-applications are isolated through a frame, a route of a second Web application is intercepted, a third route address is generated based on a route address of the second Web application, and the route of the second Web application is realized according to the third route address. Because the third routing address can represent the main application integrated by the sub-application, the influence of the routing change of the sub-application on the routing of the main application is avoided, the routing conflict between the main application and the sub-application is prevented in the frame layer, the situation that the page of the sub-application cannot be rendered or the page data after the rendering is inaccurate is further prevented, and the page rendering accuracy of the sub-application is ensured.

In addition, the common status information of at least two sub-applications with dependency relationship, such as internationalization information and user information, is registered and acquired through the message bus module 130, so as to release the forced loading sequence of the sub-applications with dependency relationship, and reduce the complexity of sub-application control, i.e. reduce the development difficulty of the framework. In addition, the framework can preload page resources of other sub-applications, such as preloading page resources of other sub-applications when the current page is in an idle period (i.e. a period which is not triggered and used), so that the efficiency of sub-application page rendering is improved when the sub-applications are switched.

The embodiment of the present application further provides a page rendering device, which is configured to execute each step in the above method, and related features may be referred to the description in the above embodiment, which is not repeated herein. Fig. 5 is a schematic structural diagram of a page rendering device according to an embodiment of the present application.

Referring to fig. 5, the apparatus includes a receiving unit 510 and a processing unit 520. The receiving unit 510 is configured to receive a first routing address, where the first routing address is sent by the browser in response to a user operation, where the user operation is used to trigger a second application on a page of a first application, the second application is a sub-application of the first application, and the first routing address is a routing address of the second application; the processing unit 520 is configured to generate a third routing address according to the first routing address and a second routing address, where the second routing address is a routing address corresponding to a page of the first application; acquiring page resources of the second application according to the third routing address; and rendering the page of the second application according to the page resource of the second application.

In some embodiments, the processing unit 520 is further configured to: and sending the third routing address to the browser so that the browser displays the third routing address in an address bar of the browser.

In some embodiments, the processing unit 520 is further configured to: before receiving a first routing address, determining tool library resources on which at least two sub-applications of the first application depend, wherein the at least two sub-applications comprise the second application; determining a common tool library resource on which the at least two sub-applications depend, the common tool library resource being an intersection of the at least two sub-application dependent tool library resources; and loading the public tool library resource.

In some embodiments, the processing unit 520 is further configured to: after receiving the first routing address, loading a first tool library resource on which the second application depends, wherein the first tool library resource is a tool library resource except the public tool library resource in the tool library resources on which the second application depends.

In some embodiments, the processing unit 520 is further configured to: before receiving a first routing address, determining a third application on which the second application depends, wherein the third application is a sub-application of the first application; loading first information; the first information is service information used by the second application and the third application.

In some embodiments, the processing unit 520 is specifically configured to: acquiring first data from a network side according to the third routing address; passing the first data and the first information to the second application; and acquiring the page resource generated by the second application according to the first data and the first information.

In some embodiments, the processing unit 520 is further configured to: after rendering the page of the second application, acquiring page resources of a fourth application, wherein the fourth application is a sub-application of the second application; and when the link of the fourth application on the page of the second application is triggered, rendering the page of the fourth application according to the page resource of the fourth application.

In a simple embodiment, one skilled in the art will appreciate that the page rendering device in the above embodiment may take the form shown in fig. 6. As shown in fig. 6, the apparatus 600 includes at least one processor 610 and an interface circuit 620. The processor 610 and the interface circuit 620 are coupled to each other. It is understood that the interface circuit 620 may be a transceiver or an input-output interface. Optionally, the apparatus 600 may further include a memory 630 for storing instructions executed by the processor 610 or for storing input data required by the processor 610 to execute instructions or for storing data generated after the processor 610 executes instructions. The specific connection medium between the processor 610 and the memory 630 is not limited in the embodiments of the present application. The processor 610 may communicate with other devices via the interface circuit 620 for data transmission.

When the apparatus 600 is used to implement the method shown in fig. 3 or fig. 4, the processor 610 is used to implement the functions of the processing unit 520, and the interface circuit 620 is used to implement the functions of the receiving unit 510.

When the apparatus 600 is applied to a chip of a terminal, the terminal chip implements the functions of the terminal device in the above-described method embodiment. The terminal chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, and the information is sent to the terminal device by the network device; alternatively, the terminal chip sends information to other modules (e.g., radio frequency modules or antennas) in the terminal device, which the terminal sends to the network device.

When the apparatus 600 is applied to a module of a network device, the network device module implements the functions of the network device in the above-described method embodiment. The network device module receives information from other modules (such as a radio frequency module or an antenna) in the network device, the information being transmitted to the network device by the terminal; alternatively, the network device module sends information to other modules in the network device (e.g., radio frequency modules or antennas), which the network device sends to the terminal device. The network device module may be a baseband chip of the network device, or may be a DU or other module, where the DU may be a DU under an open radio access network (open radio access network, O-RAN) architecture.

It is to be appreciated that the processor in embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.

It should be appreciated that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to encompass such modifications and variations.

Claims

1. A method of page rendering, the method comprising:

receiving a first routing address, wherein the first routing address is sent by a browser in response to user operation, the user operation is used for triggering a second application on a page of a first application, the second application is a sub-application of the first application, and the first routing address is a routing address of the second application;

Generating a third routing address according to the first routing address and a second routing address, wherein the second routing address is a routing address corresponding to a page of the first application;

acquiring page resources of the second application according to the third routing address;

and rendering the page of the second application according to the page resource of the second application.

2. The method of claim 1, wherein the third routing address comprises a domain name of the first routing address and a prefix, the prefix being the second routing address.

3. The method according to claim 1 or 2, further comprising:

and sending the third routing address to the browser so that the browser displays the third routing address in an address bar of the browser.

4. A method according to any of claims 1-3, characterized in that before receiving the first routing address, further comprising:

determining tool library resources on which at least two sub-applications of the first application depend, wherein the at least two sub-applications comprise the second application;

determining a common tool library resource on which the at least two sub-applications depend, the common tool library resource being an intersection of the at least two sub-application dependent tool library resources;

And loading the public tool library resource.

5. The method of claim 4, further comprising, after receiving the first routing address:

and loading a first tool library resource on which the second application depends, wherein the first tool library resource is a tool library resource except the public tool library resource in the tool library resource on which the second application depends.

6. A method according to any of claims 1-3, characterized in that before receiving the first routing address, further comprising:

determining a third application on which the second application depends, the third application being a child application of the first application;

loading first information; the first information is service information used by the second application and the third application.

7. The method of claim 6, wherein obtaining the page resources of the second application based on the third routing address comprises:

acquiring first data from a network side according to the third routing address;

passing the first data and the first information to the second application;

and acquiring the page resource generated by the second application according to the first data and the first information.

8. The method of any of claims 1-7, further comprising, after rendering the page of the second application:

acquiring page resources of a fourth application, wherein the fourth application is a sub-application of the second application;

and when the link of the fourth application on the page of the second application is triggered, rendering the page of the fourth application according to the page resource of the fourth application.

9. An apparatus comprising a receiving unit and a processing unit;

the receiving unit is used for receiving a first routing address, the first routing address is sent by the browser in response to user operation, the user operation is used for triggering a second application on a page of a first application, the second application is a sub-application of the first application, and the first routing address is a routing address of the second application;

the processing unit is used for generating a third routing address according to the first routing address and a second routing address, wherein the second routing address is a routing address corresponding to a page of the first application;

10. The apparatus of claim 9, wherein the third routing address comprises a domain name of the first routing address and a prefix, the prefix being the second routing address.

11. The apparatus according to claim 9 or 10, wherein the processing unit is further configured to:

12. The apparatus according to any one of claims 9-11, wherein the processing unit is further configured to:

before receiving a first routing address, determining tool library resources on which at least two sub-applications of the first application depend, wherein the at least two sub-applications comprise the second application;

and loading the public tool library resource.

13. The apparatus of claim 12, wherein the processing unit is further configured to:

after receiving the first routing address, loading a first tool library resource on which the second application depends, wherein the first tool library resource is a tool library resource except the public tool library resource in the tool library resources on which the second application depends.

14. The apparatus according to any one of claims 9-11, wherein the processing unit is further configured to:

before receiving a first routing address, determining a third application on which the second application depends, wherein the third application is a sub-application of the first application;

15. The apparatus according to claim 14, wherein the processing unit is specifically configured to:

passing the first data and the first information to the second application;

16. The apparatus according to any one of claims 9-15, wherein the processing unit is further configured to:

after rendering the page of the second application, acquiring page resources of a fourth application, wherein the fourth application is a sub-application of the second application;

17. A readable storage medium, characterized in that the readable storage medium comprises a program which, when run on a device, causes the device to perform the method of any of claims 1-8.

18. An apparatus, comprising: one or more processors; wherein the instructions of the one or more computer programs, when executed by the one or more processors, cause the apparatus to perform the method of any of claims 1-8.

19. A chip system comprising at least one chip and a memory, said at least one chip being coupled to said memory for reading and executing program instructions stored in said memory for implementing the method according to any of the preceding claims 1-8.

20. A computer program product, characterized in that the computer program product, when called by a computer, causes the computer to perform the method according to any of claims 1-8.