WO2022267809A1

WO2022267809A1 - Page embedding method and apparatus, storage medium and electronic device

Info

Publication number: WO2022267809A1
Application number: PCT/CN2022/095160
Authority: WO
Inventors: 郑仁杰; 王舒源; 暨灿
Original assignee: 北京有竹居网络技术有限公司
Priority date: 2021-06-21
Filing date: 2022-05-26
Publication date: 2022-12-29
Also published as: CN113296762B; CN113296762A

Abstract

The present disclosure relates to a page embedding method and apparatus, a storage medium and an electronic device, the method comprising: installing a front-end function package in a first page system, the front-end function package packaging a functional function which is needed in a page embedding process and which is called by means of a custom page embed label; acquiring a page address of a second page to be embedded; determining parameters of the custom page embed label according to the page address of the second page, and calling the front-end function package by means of the custom page embed label after having the parameters introduced, so as to obtain a page module instance, wherein a message interface of the page module instance supports message transmission by using a non-character-string means; and embedding the second page into the first page system by means of the page module instance. Therefore, page embedding may be achieved by means of a custom page embed label, a resource loading problem which exists due to performing page embedding by means of an iframe label is solved, and non-character-string message transmission between an embedding party and an embedded system is achieved.

Description

Page embedding method, device, storage medium and electronic equipment

Cross References to Related Applications

This application claims the priority of the Chinese patent application with the application number 202110686401.7 and the title of the invention "page embedding method, device, storage medium and electronic equipment" filed on June 21, 2021, the entire content of which is incorporated by reference in this application.

technical field

The present disclosure relates to the field of computer technology, and in particular, to a page embedding method, device, storage medium and electronic equipment.

Background technique

Page modular reuse refers to quickly embedding a system or a page in a system into other systems as a similar component, such as the ability of a third-party system to embed a similar business cashier interface, or Or some systems hope to embed some chart analysis capabilities of other platforms.

In related technologies, if you want to embed another page in the page system, it is mainly realized through the Iframe tag natively provided by the browser. However, when the page is embedded through the Iframe tag, the resource loading is slow, and because the browser uses inter-process communication, and the inter-process communication restricts the use of serialized strings in the underlying implementation of the computer, so the to-be-embedded The page and the embedded page can only exchange messages in the form of serializable strings, and the format of message transmission is limited, which cannot flexibly meet the needs of various scenarios.

Contents of the invention

This Summary is provided to introduce a simplified form of concepts that are described in detail later in the Detailed Description. This summary of the invention is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to be used to limit the scope of the claimed technical solution.

In a first aspect, the present disclosure provides a page embedding method, the method comprising:

Installing the front-end function package in the first page system, the front-end function package encapsulates the function functions required in the page embedding process and called by the custom page embedding label;

Obtain the page address of the second page to be embedded;

Determine the parameters of the custom page embedding tag according to the page address of the second page, and call the front-end function package through the custom page embedding tag passed in the parameters to obtain a page module instance, wherein the The message interface of the page module instance supports message passing in the form of non-string;

The second page is embedded into the first page system through the page module instance.

In a second aspect, the present disclosure provides a page embedding device, the device comprising:

The installation module is used to install the front-end function package in the first page system, and the front-end function package encapsulates the function functions required in the page embedding process and called by custom page embedding tags;

An acquisition module, configured to acquire the page address of the second page to be embedded;

The calling module is used to determine the parameters of the custom page embedding tag according to the page address of the second page, and call the front-end function package through the custom page embedding tag passed in the parameters to obtain the page module Instance, wherein the message interface of the page module instance supports message transmission in the form of non-character strings;

An embedding module, configured to embed the second page into the first page system through the page module instance.

In a third aspect, the present disclosure provides a non-transitory computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the method described in the first aspect are implemented.

In a fourth aspect, the present disclosure provides an electronic device, including:

a memory on which a computer program is stored;

A processor configured to execute the computer program in the memory to implement the steps of the method in the first aspect.

Through the above technical solution, the front-end function package can be installed in the first page system. The front-end function package encapsulates the function functions required in the page embedding process and is called through the custom page embedding tag, so that the user can subsequently use the custom page The embed tag and the front-end feature pack embed the second page into the first page system. Thus, page embedding can be performed without relying on the native Iframe tag of the browser, thereby solving the resource loading problem existing in page embedding through the Iframe tag. Moreover, the message interface of the page module instance obtained by calling the front-end function package can be transmitted in the form of a non-string, so that the communication between the first page system and the second page to be embedded can be carried out in the form of a non-string Message passing, and then realize more complex page message interaction logic, to meet the usage requirements in different scenarios.

Other features and advantages of the present disclosure will be described in detail in the detailed description that follows.

Description of drawings

The above and other features, advantages and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic and that elements and elements are not necessarily drawn to scale. In the attached picture:

Fig. 1 is a flowchart of a page embedding method according to an exemplary embodiment of the present disclosure;

Fig. 2 is a block diagram of a page embedding device according to an exemplary embodiment of the present disclosure;

Fig. 3 is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure.

detailed description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the drawings, it should be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein; A more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for exemplary purposes only, and are not intended to limit the protection scope of the present disclosure.

It should be understood that the various steps described in the method implementations of the present disclosure may be executed in different orders, and/or executed in parallel. Additionally, method embodiments may include additional steps and/or omit performing illustrated steps. The scope of the present disclosure is not limited in this respect.

As used herein, the term "comprise" and its variations are open-ended, ie "including but not limited to". The term "based on" is "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one further embodiment"; the term "some embodiments" means "at least some embodiments." Relevant definitions of other terms will be given in the description below.

It should be noted that concepts such as "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the sequence of functions performed by these devices, modules or units or interdependence. In addition, it should be noted that the modifications of "a" and "plurality" mentioned in the present disclosure are illustrative and not restrictive. Those skilled in the art should understand that unless the context clearly indicates otherwise, it should be understood as "a or more".

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are used for illustrative purposes only, and are not used to limit the scope of these messages or information.

As mentioned in the background art, in related technologies, if you want to embed another page in the page system, it is mainly realized through the Iframe tag natively provided by the browser. However, Iframe is an old technology launched by browsers more than ten years ago. With the industry's technology updates and iterations, page embedding through Iframe tags has exposed many problems in the current background. For example, the performance bottleneck, every time you switch between the embedded page and the embedded page, you need to reload the page resources completely, resulting in slow resource loading efficiency. And because the browser uses inter-process communication, and inter-process communication is limited to the use of serialized strings in the underlying implementation of the computer, so the page to be embedded and the page to be embedded can only be serialized Message interaction in the form of character strings, and the format of message transmission is limited, which cannot flexibly meet the usage requirements in various scenarios.

The inventor found through research that there is another page embedding method through the portal tag in the related art. Specifically, a src attribute can be attached to the portal tag, and the value corresponding to the attribute is the subsystem page to be embedded. In this way, the tag can be placed anywhere in the system that needs to embed the subpage to realize page embedding. However, this method still does not solve the problem that the Iframe tag cannot transmit non-string type data, and the premise that the embedding party and the embedded system want to establish message communication is to ensure that the domain names of the two are exactly the same. That is to say, there is also the problem of limited communication between the embedding party and the embedded system through the portal tag.

In view of this, the present disclosure provides a page embedding method to implement page embedding by customizing page embedding tags, solve the resource loading problem existing in page embedding through Iframe tags, and realize the non-uniformity between the embedding party and the embedded system. String messaging improves the applicability of page embedding scenarios.

Fig. 1 is a flowchart of a page embedding method according to an exemplary embodiment of the present disclosure. Referring to Figure 1, the page embedding method includes:

Step 101, install the front-end function package in the first page system, the front-end function package encapsulates the functions required in the page embedding process and called by custom page embedding tags.

Step 102, obtaining the page address of the second page to be embedded.

Step 103: Determine the parameters of the custom page embed tag according to the page address of the second page, and call the front-end function package through the custom page embed tag after passing in the parameters to obtain a page module instance whose message interface supports Message passing in non-string form.

Step 104, embedding the second page into the first page system through the page module instance.

Exemplarily, the front-end function package may be pre-packaged with functions required by the page embedding process and invoked through custom page embedding tags, such as page resource loading functions and the like. Therefore, after the front-end function package is installed in the first page system, the page resource loading function can be called to load resources. That is to say, the corresponding resources can be loaded in advance, so that there is no need to reload resources during each page switching process, which can solve the problem of resource loading existing in page embedding through Iframe tags. It should be understood that the function functions in the front-end function package may be set according to the actual situation, and may include various types of micro-front-end basic function functions, which are not limited in the implementation of the present disclosure.

After the front-end function package is installed in the first page system, the page address of the second page to be embedded can be obtained, for example, the page address of the second page can be obtained from the address bar of the browser displaying the second page, the embodiment of the present disclosure There is no limit to this. Then, parameters of the custom page embedding tag can be determined according to the page address of the second page.

Exemplarily, the custom page embedding tag can be understood as a hypertext markup language HTML tag used to call a pre-packaged function in the front-end function package. That is to say, in the embodiment of the present disclosure, a kind of HTML tag is customized, and a front-end function package corresponding to the HTML tag is preset, so that the custom page embedding can be completed by calling the function function in the front-end function package The page display function corresponding to the label. Moreover, it should be understood that when a user embeds a page using the traditional Iframe solution in related technologies, in the most ideal case (there is no need for business communication between the embedding party and the embedded party and some specific business logic), the The embedding party does not need to carry out any modification, and only needs to pass the address of the embedded page to the src interface attribute of the Iframe tag when embedding. Similarly, in the embodiment of the present disclosure, such an effect can also be achieved by embedding tags on the custom page in the most ideal case, so that for long-term unmaintained historical systems or for external uncontrollable pages, zero Cost transformation design, reducing the operation process of page embedding.

In a possible manner, determining the parameters of the custom page embed tag according to the page address of the second page may be: using the page address of the second page as the parameter of the custom page embed tag; or, according to the page address of the second page. Resource parsing, obtain the structured data address of the completed resource parsing, and use the structured data address as a parameter of the custom page embedding tag.

It should be understood that traditional HTML parsing requires a built-in HTML code parser, and the parser will bring more codes to be parsed at runtime, and even just adding a line of code at runtime will bring additional performance consumption. And the parser will parse the user's incoming HTML file sentence by sentence, which further increases additional performance overhead. Therefore, the embodiments of the present disclosure can reduce performance consumption by passing the address of the structured data that has completed resource resolution.

For example, by referring to the same processing function, the runtime parsing cost can be transferred to compile time, so as to ensure that there is no difference between the content parsed at compile time and the content parsed at runtime, and reduce runtime performance consumption. In addition, the general execution function of PuzzleWebpackPlugin can be used to enable direct transmission of the structured data address of the completed resource analysis during the page embedding process with less code writing. As a result, the running cost can be reduced and the code running performance can be improved.

For example, if the custom embedded tag is named magic-portal tag, and the page address of the second page to be embedded is https://example.com/, then the page address of the second page can be used as the custom embedded tag in the following manner Parameters: <magic-portal html="https://example.com/"></magic-portal>. Or, you can first perform resource analysis based on the page address of the second page to obtain the structured address of the completed resource analysis, and then use the structured data address as a parameter of the custom page embedding tag in the following manner: <magic-portal manifest= "https://example.com/puzzle-manifest.json"></magic-portal>. Therefore, in addition to directly introducing the page address of the second page through the html field, the custom embedded tag can also pass a structured data address that has completed resource parsing through the manifest field, reducing performance and running consumption.

After determining the parameters of the custom page embed tag according to the page address of the second page, that is, after passing in the corresponding parameters to the custom page embed tag, the front-end function package can be called through the custom page embed tag to obtain a page module instance, The message interface of the page module instance supports message transmission in the form of non-character strings.

It should be understood that in the related art, the page embedding is performed through the Iframe tag, and the message communication capability provided by the early message event of the browser is mainly reused in the process of message transmission to complete the data transmission of the event. Therefore, in the Iframe embedding scheme, both the embedder and the embedded party can dispatch message events with corresponding specific business data, or listen to whether someone else dispatches message events to obtain the data attached to the other party to complete some specific tasks. the behavior of. However, because this method uses inter-process communication, and inter-process communication is limited to the use of serialized strings in the underlying implementation of the computer, so the link between the page to be embedded and the page to be embedded can only be serialized Message interaction in the form of character strings, and the format of message transmission is limited, which cannot flexibly meet the usage requirements in various scenarios.

However, in the embodiments of the present disclosure, in the event dispatch mechanism, that is, in the event communication process, combined with the memory management mechanism, the constraints of the original event dispatch can be broken, and any custom event can be dispatched through a simple interface method. As a result, the format of the transferred data will no longer be restricted. For example, pointer data that is not a string type and cannot be serialized normally can also be transferred in this way.

In a possible way, the message event can be delivered to the second page through the first message interface of the page module instance and the event dispatching mechanism, wherein the message event to be delivered is stored in the memory when the event is dispatched, so that the second page can retrieve the message from the memory Get the message event. Or, listen to the message event passed by the second page through the second message interface and the event dispatching mechanism of the page module instance, wherein the second page stores the message event to be transferred in the memory when dispatching the event, so that the first page system receives the event Get the message event from the memory at the time.

For example, if it is desired to pass a message event from the embedded first page system to the embedded second page, the message event can be passed to the second page through the postMessage interface of the page module instance (that is, the first message interface) and the event dispatch mechanism, The message event to be delivered can be stored in the memory when the event is dispatched, so that the second page can obtain the message event from the memory. Or, if the embedded first page system is expected to listen to the message event from the embedded second page, you can listen to the message event delivered by the second page through the addEventListener interface of the page module instance (that is, the second message interface) and the event dispatch mechanism , where the second page can store the message event to be delivered in the memory when dispatching the event, so that the system of the first page can obtain the message event from the memory when receiving the event. Thus, the memory management mechanism can be used to implement message transmission between the first page system and the second page, thereby solving the problem of communication limitation between the first page system and the second page.

In practical applications, in addition to the message event, other types of custom events may also need to be delivered. In this regard, the embodiments of the present disclosure provide a third message interface and a fourth message interface for the custom event, so as to perform message transmission of corresponding data types through different types of message interfaces, thereby improving message transmission efficiency.

That is to say, in a possible manner, page messages other than the message event can be delivered to the second page through the third message interface of the page module instance and the event delivery mechanism, wherein the page message to be delivered can be sent when the event is delivered Stored in memory so that the second page gets page messages from memory. Or, monitor the page messages delivered by the second page, except the message event, through the fourth message interface and the event dispatching mechanism of the page module instance, wherein the second page can store the page message to be delivered in the memory when dispatching the event, so that The first page system fetches page messages from memory when an event is received.

For example, if it is desired to pass a general custom event from the embedded first page system to the embedded second page, the second page can be sent to the second page through the general emitEvent interface (ie, the third message interface) Pass the custom event, where the custom event to be passed can be stored in memory when the event is dispatched, so that the second page can obtain the custom event from the memory. Or, if it is desired that the embedded first page system listens to custom events from the embedded second page, you can listen to the second page delivered by the page module instance through the addPortalEventListener interface (that is, the fourth message interface) and the event dispatch mechanism. The custom event, wherein the second page can store the custom event to be delivered in memory when dispatching the event, so that the system of the first page can obtain the custom event from the memory when receiving the event.

As a result, the message transmission of custom events can be realized between the first page system and the second page through the memory management mechanism, which can not only meet the page communication requirements in various scenarios, but also solve the problem of limited communication between pages.

It should be understood that, in a possible manner, the third message interface and the fourth message interface may also be used to transmit message events, but the first message interface and the second message interface may only be used to transmit message events. In addition, in addition to providing various message interfaces for the first page system to transmit messages to the second page or monitor messages from the second page, the page module instance can also inject global interface objects into the global environment of the page module instance, so that The page module instance has the capability of transmitting messages from the second page to the first page system or monitoring messages from the first page system. For example, the second page can transmit message data to the first page system through the fifth message interface on the page module instance, or the second page can listen to events triggered by the first page system through the sixth message interface on the page module instance.

In practical applications, the content or functions of various parts of a front-end system are often switched or scheduled through routing or page jumps, and at the same time as page switching and jumping, they are often accompanied by the content in the browser address bar. address change. For example, a commercial platform has a cash register system that supports payment-related business logic, and often completes a complete payment process, which generally requires jumping through the following pages: confirmation information on the order page, input payment method on the bank card page, etc. Data and payment completion pages, each page usually has its own page address and completes the jump according to the user's operation (next step or return to the previous step). Or, on the front-end page, switch functions and navigate through routing jumps.

However, routing jumps may not meet expectations in many cases. For example, in a system page similar to a mall platform, the cash register system is only embedded in the page of the mall platform as a called third-party module. A small part of , or just a pop-up window, at this time the address of the mall page is a link to the product. If the cashier module is evoked or some cashier operations cause the page address to change, it is often not as expected, because most of the content on the page is still product details, and because a small part of the content on the page (that is, the cashier module ) causes the address of the browser to change, which is not in line with the user's intuition. Therefore, routing isolation between the embedded party and the embedded party is necessary.

Most of the micro-frontend solutions in related technologies expect the addresses of the embedding party and the embedded party to be consistent under any circumstances. In view of this, in order to support front-end routing scenarios under different business systems, the embodiments of the present disclosure provide two strategies of route isolation and route non-isolation, which can be configured through parameters during the implementation of the present disclosure to determine route isolation and route non-isolation isolation.

In a possible manner, the routing parameter may be obtained first, and the routing parameter is used to represent the routing status of the first page system and the second page, and the routing status includes a routing isolation enabled state or a routing isolation disabled state. If the routing parameter indicates that the routing isolation is enabled, then determine the custom routing information of the second page, and control the routing of the second page according to the custom routing information, so that after the second page is embedded in the system of the first page, the The routing is different from the routing of the first page system. If the route parameter represents the route isolation closed state, then control the route of the second page according to the route information of the first page system, so that after the second page is embedded in the first page system, the route of the second page is the same as the route of the first page system same.

That is to say, the custom page embed tag can have a routing parameter, so that the routing status of the first page system and the second page can be determined by configuring the routing parameter in the custom page embed tag. For example, if routing parameters are configured, it is determined that the routing status of the first page system and the second page is the route isolation enabled state; otherwise, if no routing parameters are configured, then the routing status of the first page system and the second page is determined Isolation off state for routing. For example, the embedded tag of the custom page is named magic-portal tag. If the routing parameter history-isolation is configured as follows, it can be determined that the routing status of the system on the first page and the routing status of the second page are route isolation enabled: <magic- portal history-isolation></magic-portal>. Conversely, if the routing parameter history-isolation is not configured, the routing status of the system on the first page and the routing status of the second page can be determined as routing isolation disabled.

After obtaining the routing parameters, if the routing parameters indicate that the routing isolation is enabled, the custom routing information of the second page can be determined, and the routing of the second page can be controlled according to the custom routing information, so that the second page embeds the second page. The route of the second page after the first page system is different from the route of the first page system. Wherein, the custom routing information is used to represent the routing information of the second page, and may be obtained when the page address of the second page is obtained, which is not limited in this embodiment of the present disclosure. Then, when the route isolation is turned on, the custom route information can make the route of the second page after the second page is embedded in the first page system different from the route of the first page system. Therefore, after the second page is embedded, the page address displayed by the first page system in the address bar of the browser may not change, which reduces the impact of page embedding on the first page system and improves user perception.

If the route parameter represents the route isolation closed state, the route of the second page can be controlled according to the route information of the first page system, so that after the second page is embedded in the first page system, the route of the second page is the same as that of the first page system. Routing is the same. It should be understood that in this case, the second page can declare its own namespace namespace on the first page system, so that the routing of the second page can be consistent with the first page system, otherwise there may be a second page in the routing process. The second page will not find the page resource problem. For example, the system on the first page has completed the switch from /home to /about, and the second page will also perform the same process, but if the second page does not implement the /about page, the corresponding page cannot be found. In this case, if the second page maintains its own namespace namespace on the first page system in advance, the routing process can be synchronized for the same page corresponding to the second page and the first page system, and vice versa. Perform routing synchronization to avoid the problem that the second page cannot find page resources.

Next, the second page can be embedded into the first page system according to the page module instance. In a possible way, you can first obtain the custom display parameters for the second page, and then pass the custom display parameters into the page module instance to obtain the target page module instance, and finally embed the second page into the second page module instance according to the target page module instance One page system.

For example, the custom display parameters are used to define the display style or display content of the second page embedded in the first page system, which can be set according to the actual situation, such as including parameters for injecting metadata into the first page system, etc. , which is not limited in the embodiments of the present disclosure. In specific implementation, the external interface for custom display can be set for the page module instance, and the parameter rules of the external interface can be set, so that the corresponding custom display parameters can be passed in according to the parameters required by the external interface. That is, obtain the custom display parameters for the second page, and pass the custom display parameters into the page module instance, so as to realize the custom display configuration of the second page and meet the page embedding requirements in various scenarios. That is to say, the embodiment of the present disclosure can add customized parameters and configuration information to the page module instance through the interface provided by the page module instance, so as to realize customized capabilities or presentations.

After obtaining the target page module instance, the second page can be embedded into the first page system according to the target page module instance. In a possible manner, it is possible to first determine to place the page module instance at the target display position of the first page system, and then display the second page at the target display position of the first page system after the page module instance completes resource loading and initialization operations .

For example, the target display position may be set according to actual conditions, which is not limited in this embodiment of the present disclosure. It should be understood that in the embodiment of the present disclosure, a front-end function package is pre-packaged for custom page embedding tags, so the page module instance is placed in any desired position of the embedded page, and the page module instance will automatically complete resource loading and Internal initialization, so that after the resource loading and initialization operations of the page module instance are completed, the second page can be displayed at the target display position of the first page system. As a result, page embedding can be realized by customizing the page embedding tag, solving the resource loading problem existing in page embedding through Iframe tags, and realizing non-string message transmission between the embedding party and the embedded system, improving the scene of page embedding applicability.

Based on the same inventive concept, an embodiment of the present disclosure provides a page embedding device, which can become part or all of an electronic device through software, hardware or a combination of both. Referring to FIG. 2, the page embedding device 200 includes:

The installation module 201 is used to install the front-end function package in the first page system, and the front-end function package encapsulates the function functions required in the page embedding process and called by custom page embedding tags;

Obtaining module 202, configured to obtain the page address of the second page to be embedded;

The calling module 203 is configured to determine the parameters of the custom page embedding tag according to the page address of the second page, and call the front-end function package through the custom page embedding tag passed in the parameters to obtain the page A module instance, wherein the message interface of the page module instance supports message transmission in the form of a non-character string;

The embedding module 204 is configured to embed the second page into the first page system through the page module instance.

Optionally, the device 200 also includes:

The first communication module is configured to transmit the message event to the second page through the first message interface and the event distribution mechanism of the page module instance after obtaining the page module instance, wherein the message event to be transmitted is sent when the event is dispatched The message event is stored in the memory, so that the second page obtains the message event from the memory;

The second communication module is configured to listen to the message event delivered by the second page through the second message interface of the page module instance and the event distribution mechanism, wherein the second page will send the message to be delivered when the event is dispatched The event is stored in the memory, so that the first page system obtains the message event from the memory when receiving the event.

Optionally, the device 200 also includes:

The third communication module is configured to transmit page messages other than the message event to the second page through the third message interface and the event distribution mechanism of the page module instance after obtaining the page module instance, wherein the event is dispatched storing the page message to be delivered in the memory, so that the second page obtains the page message from the memory;

The fourth communication module is configured to monitor the page messages delivered by the second page, except the message event, through the fourth message interface of the page module instance and the event distribution mechanism, wherein the second page will send the event when dispatching the event. The page message to be delivered is stored in memory, so that the first page system acquires the page message from memory when receiving an event.

Optionally, the device 200 also includes:

A first parameter acquisition module, configured to acquire routing parameters, the routing parameters are used to characterize the routing status of the first page system and the second page, and the routing status includes a routing isolation enabled state or a routing isolation disabled state;

The first determining module is configured to determine the custom routing information of the second page when the routing parameter indicates that the routing isolation is enabled, and control the routing of the second page according to the custom routing information, After the second page is embedded in the first page system, the route of the second page is different from the route of the first page system;

The second determining module is configured to control the routing of the second page according to the routing information of the first page system when the routing parameter indicates that the routing isolation is off, so that the second page is embedded in the The route of the second page after the first page system is the same as the route of the first page system.

Optionally, the calling module 203 is used for:

using the page address of the second page as a parameter of the custom page embedding tag; or

Resource parsing is performed according to the page address of the second page to obtain a structured data address that has completed resource parsing, and the structured data address is used as a parameter of the custom page embedding tag.

Optionally, the device 200 also includes:

A second parameter acquisition module, configured to acquire custom display parameters for the second page, and pass the custom display parameters into the page module instance to obtain a target page module instance;

The embedded module 204 is used for:

Embedding the second page into the first page system according to the target page module instance.

Optionally, the embedding module 204 is used for:

determining to place the page module instance at a target display position of the first page system;

After the resource loading and initialization operations are completed by the page module instance, the second page is displayed at the target display position of the first page system.

Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Based on the same inventive concept, an embodiment of the present disclosure further provides a non-transitory computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of any one of the above page embedding methods are implemented.

Based on the same inventive concept, an embodiment of the present disclosure also provides an electronic device, including:

a memory on which a computer program is stored;

A processor, configured to execute the computer program in the memory, so as to realize the steps of any page embedding method described above.

Referring now to FIG. 3 , it shows a schematic structural diagram of an electronic device 300 suitable for implementing an embodiment of the present disclosure. The terminal equipment in the embodiment of the present disclosure may include but not limited to such as mobile phone, notebook computer, digital broadcast receiver, PDA (personal digital assistant), PAD (tablet computer), PMP (portable multimedia player), vehicle terminal (such as mobile terminals such as car navigation terminals) and fixed terminals such as digital TVs, desktop computers and the like. The electronic device shown in FIG. 3 is only an example, and should not limit the functions and scope of use of the embodiments of the present disclosure.

As shown in FIG. 3 , an electronic device 300 may include a processor (such as a central processing unit, a graphics processing unit, etc.) (RAM) 303 to execute various appropriate actions and processing. In the RAM 303, various programs and data necessary for the operation of the electronic device 300 are also stored. The processor 301, ROM 302, and RAM 303 are connected to each other through a bus 304. An input/output (I/O) interface 305 is also connected to the bus 304 .

Typically, the following devices can be connected to the I/O interface 305: input devices 306 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speaker, vibrating an output device 307 such as a computer; a memory 308 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 309. The communication means 309 may allow the electronic device 300 to perform wireless or wired communication with other devices to exchange data. While FIG. 3 shows electronic device 300 having various means, it should be understood that implementing or having all of the means shown is not a requirement. More or fewer means may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product, which includes a computer program carried on a non-transitory computer readable medium, where the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 309, or from memory 308, or from ROM 302. When the computer program is executed by the processor 301, the above functions defined in the methods of the embodiments of the present disclosure are executed.

It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can transmit, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted by any appropriate medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

In some embodiments, any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol) can be used to communicate, and can communicate with digital data in any form or medium (for example, communication network) interconnection. Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network of.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device, or may exist independently without being incorporated into the electronic device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device: installs a front-end function package in the first page system, and the front-end function package encapsulates The function function required in the page embedding process and called by the custom page embedding tag; obtaining the page address of the second page to be embedded; determining the parameters of the custom page embedding tag according to the page address of the second page, And call the front-end function package by passing in the custom page embedding tag after the parameters to obtain a page module instance, wherein the message interface of the page module instance supports message transmission in the form of a non-character string; through the A page module instance embeds the second page into the first page system.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, or combinations thereof, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and Includes conventional procedural programming languages - such as "C" or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, using an Internet service provider to connected via the Internet).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code that contains one or more logical functions for implementing specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified functions or operations , or may be implemented by a combination of dedicated hardware and computer instructions.

The modules involved in the embodiments described in the present disclosure may be implemented by software or by hardware. Wherein, the name of the module does not constitute a limitation on the module itself under certain circumstances.

The functions described herein above may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), System on Chips (SOCs), Complex Programmable Logical device (CPLD) and so on.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer discs, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

According to one or more embodiments of the present disclosure, Example 1 provides a page embedding method, the method comprising:

Obtain the page address of the second page to be embedded;

According to one or more embodiments of the present disclosure, Example 2 provides the method of Example 1. After obtaining the page module instance, the method further includes:

Pass the message event to the second page through the first message interface of the page module instance and the event distribution mechanism, wherein when dispatching the event, store the message event to be transferred into the memory, so that the second page can retrieve the message from the memory Get the message event in;

Monitor the message event delivered by the second page through the second message interface of the page module instance and the event distribution mechanism, wherein the second page stores the message event to be delivered in memory when dispatching the event, so that The first page system obtains the message event from the memory when receiving the event.

According to one or more embodiments of the present disclosure, Example 3 provides the method of Example 1 or 2. After obtaining the page module instance, the method further includes:

Pass the page message except the message event to the second page through the third message interface of the page module instance and the event distribution mechanism, wherein when the event is dispatched, the page message to be transmitted is stored in the memory, so that the The second page obtains the page message from memory;

Through the fourth message interface of the page module instance and the event distribution mechanism, monitor the page message delivered by the second page, except for the message event, wherein the second page will send the page message to be delivered when the event is dispatched Stored in the memory, so that the first page system acquires the page message from the memory when receiving an event.

According to one or more embodiments of the present disclosure, Example 4 provides the method of Example 1 or 2, the method further comprising:

Acquiring routing parameters, the routing parameters are used to characterize the routing status of the first page system and the second page, and the routing status includes a routing isolation enabled state or a routing isolation disabled state;

If the routing parameter indicates that the routing isolation is enabled, then determine the custom routing information of the second page, and control the routing of the second page according to the custom routing information, so that the second page After embedding the first page system, the route of the second page is different from the route of the first page system;

If the routing parameter represents the routing isolation off state, then control the routing of the second page according to the routing information of the first page system, so that after the second page is embedded in the first page system, the The route of the second page is the same as the route of the first page system.

According to one or more embodiments of the present disclosure, Example 5 provides the method of Example 1 or 2, determining parameters of the custom page embedding tag according to the page address of the second page, including:

According to one or more embodiments of the present disclosure, Example 6 provides the method of Example 1 or 2, the method further comprising:

Acquire custom display parameters for the second page, and pass the custom display parameters into the page module instance to obtain a target page module instance;

Embedding the second page into the first page system according to the page module instance includes:

According to one or more embodiments of the present disclosure, Example 7 provides the method of Example 1 or 2, embedding the second page into the first page system according to the page module instance, including:

After the resource loading and initialization operations of the page module instance are completed, the second page is displayed at the target display position of the first page system.

According to one or more embodiments of the present disclosure, Example 8 provides a page embedding device, the device comprising:

According to one or more embodiments of the present disclosure, Example 9 provides a non-transitory computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, any one of Examples 1-7 can be implemented. steps of the method described above.

According to one or more embodiments of the present disclosure, Example 10 provides an electronic device, comprising:

a memory on which a computer program is stored;

A processor, configured to execute the computer program in the memory, so as to implement the steps of any one of the methods in Examples 1-7.

The above description is only a preferred embodiment of the present disclosure and an illustration of the applied technical principles. Those skilled in the art should understand that the disclosure scope involved in this disclosure is not limited to the technical solution formed by the specific combination of the above-mentioned technical features, but also covers the technical solutions formed by the above-mentioned technical features or Other technical solutions formed by any combination of equivalent features. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

In addition, while operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or performed in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while the above discussion contains several specific implementation details, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims. Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Claims

A page embedding method, characterized in that the method comprises:

Installing the front-end function package in the first page system, the front-end function package encapsulates the function functions required in the page embedding process and called by the custom page embedding label;

Obtain the page address of the second page to be embedded;

Determine the parameters of the custom page embedding tag according to the page address of the second page, and call the front-end function package through the custom page embedding tag passed in the parameters to obtain a page module instance, wherein the The message interface of the page module instance supports message passing in the form of non-string;

The second page is embedded into the first page system through the page module instance.
The method according to claim 1, wherein after obtaining the page module instance, the method further comprises:

Pass the message event to the second page through the first message interface of the page module instance and the event distribution mechanism, wherein when dispatching the event, store the message event to be transferred into the memory, so that the second page can retrieve the message from the memory Get the message event in;

Monitor the message event delivered by the second page through the second message interface of the page module instance and the event distribution mechanism, wherein the second page stores the message event to be delivered in memory when dispatching the event, so that The first page system obtains the message event from the memory when receiving the event.
The method according to claim 1 or 2, wherein after obtaining the page module instance, the method further comprises:

Pass the page message except the message event to the second page through the third message interface of the page module instance and the event distribution mechanism, wherein when the event is dispatched, the page message to be transmitted is stored in the memory, so that the The second page obtains the page message from memory;

Through the fourth message interface of the page module instance and the event distribution mechanism, monitor the page message delivered by the second page, except for the message event, wherein the second page will send the page message to be delivered when the event is dispatched Stored in the memory, so that the first page system acquires the page message from the memory when receiving an event.
The method according to claim 1 or 2, characterized in that the method further comprises:

Acquiring routing parameters, the routing parameters are used to characterize the routing status of the first page system and the second page, and the routing status includes a routing isolation enabled state or a routing isolation disabled state;

If the routing parameter indicates that the routing isolation is enabled, then determine the custom routing information of the second page, and control the routing of the second page according to the custom routing information, so that the second page After embedding the first page system, the route of the second page is different from the route of the first page system;

If the routing parameter represents the routing isolation off state, then control the routing of the second page according to the routing information of the first page system, so that after the second page is embedded in the first page system, the The route of the second page is the same as the route of the first page system.
The method according to claim 1 or 2, wherein determining the parameters of the custom page embedding tag according to the page address of the second page includes:

using the page address of the second page as a parameter of the custom page embedding tag; or

Resource parsing is performed according to the page address of the second page to obtain a structured data address that has completed resource parsing, and the structured data address is used as a parameter of the custom page embedding tag.
The method according to claim 1 or 2, characterized in that the method further comprises:

Acquire custom display parameters for the second page, and pass the custom display parameters into the page module instance to obtain a target page module instance;

Embedding the second page into the first page system according to the page module instance includes:

Embedding the second page into the first page system according to the target page module instance.
The method according to claim 1 or 2, wherein embedding the second page into the first page system according to the page module instance comprises:

determining to place the page module instance at a target display position of the first page system;

After the resource loading and initialization operations of the page module instance are completed, the second page is displayed at the target display position of the first page system.
A page embedding device, characterized in that the device comprises:

The installation module is used to install the front-end function package in the first page system, and the front-end function package encapsulates the function functions required in the page embedding process and called by custom page embedding tags;

An acquisition module, configured to acquire the page address of the second page to be embedded;

The calling module is used to determine the parameters of the custom page embedding tag according to the page address of the second page, and call the front-end function package through the custom page embedding tag passed in the parameters to obtain the page module Instance, wherein the message interface of the page module instance supports message transmission in the form of non-character strings;

An embedding module, configured to embed the second page into the first page system through the page module instance.
A non-transitory computer-readable storage medium, on which a computer program is stored, characterized in that, when the program is executed by a processor, the steps of the method in any one of claims 1-7 are implemented.
An electronic device, characterized in that it comprises:

a memory on which a computer program is stored;

A processor, configured to execute the computer program in the memory, so as to implement the steps of the method according to any one of claims 1-7.