Data calling method, device, electronic device and computer storage medium

Abstract

The embodiment of the present application provides a data calling method, device, electronic device and computer storage medium, wherein the data calling method includes: when the first page is loaded in the first container, if the first page needs to call the data of the second page, register the preset interface of the first container as the listener of the second page in the page stack manager; the page stack manager jumps to the second page in response to the request to jump to the second page, and uses the second container to load the second page; when the preset interface listens to the return result event of the second page, the page stack manager is used to call back the data of the second page to the first container through the preset interface; and the first page is loaded using the data of the first container and the second page. Data communication between containers is realized, and it does not need to be developed separately, so its application range is wider, and it is very convenient to implement, which reduces the development cost.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer software technology, and in particular to a data calling method, device, electronic device and computer storage medium. Background Art

[0002] In applications (English: Application, App), dynamic pages are usually used to integrate dynamically changing functional services. Different dynamic pages need to be carried by different containers. In order to reduce the size of the application, there is a demand for functional reuse between different containers. However, due to the differences in the implementation mechanisms of different containers, there is a problem that different containers cannot directly communicate data. To solve this problem, in related technologies, data communication between different containers is achieved through bridging. However, in the bridging solution, different bridging methods need to be developed for each specific scenario, and the development cost is relatively high. Summary of the invention

[0003] In view of this, embodiments of the present application provide a data calling method, device, electronic device and computer storage medium to solve some or all of the above problems.

[0004] According to a first aspect of an embodiment of the present application, a data calling method is provided, including: when a first page is loaded in a first container, if the first page needs to call data of a second page, registering a preset interface of the first container as a listener of the second page in a page stack manager; in response to a request to jump to the second page, the page stack manager jumps to the second page and loads the second page using the second container; when the preset interface listens to a return result event of the second page, using the page stack manager to call back the data of the second page to the first container through the preset interface; and loading the first page using the data of the first container and the second page.

[0005] According to a second aspect of an embodiment of the present application, a data calling device is provided, including: a registration module, used to register a preset interface of the first container as a listener of the second page in a page stack manager when a first page is loaded in a first container, if the first page needs to call data of a second page; a page management module, used for the page stack manager to jump to the second page in response to a request to jump to the second page, and load the second page using the second container; a listening module, used to use the page stack manager to call back the data of the second page to the first container through the preset interface when the preset interface listens to a return result event of the second page; and a page management module, used to load the first page using the data of the first container and the second page.

[0006] According to the third aspect of an embodiment of the present application, there is provided an electronic device comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform an operation corresponding to the data calling method of the first aspect.

[0007] According to a fourth aspect of an embodiment of the present application, a computer storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the data calling method of the first aspect is implemented.

[0008] The data calling method, device, electronic device and computer storage medium provided in the embodiments of the present application, when using the first container to load the first page, if the first page needs to call the data of the second page, by registering the preset interface of the first container as the listener of the second page in the page stack manager, the second page is listened to using the preset interface, and when the return result event of the second page is listened to, the data of the second page can be called back to the first container through the page stack manager and the preset interface, thereby realizing data communication between containers, and registering an interface as the listener of a certain page does not need to be developed separately, so its application range is wider, and it is very convenient to implement, thereby reducing development costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0010] Figure 1 A schematic diagram of a scenario of a data calling method provided in Example 1 of the present application;

[0011] Figure 2 A flowchart of a data calling method provided in Example 1 of the present application;

[0012] Figure 3 A schematic diagram of a page stack provided in Example 1 of the present application;

[0013] Figure 4 A schematic diagram of another data calling method provided in the first embodiment of the present application;

[0014] Figure 5 A structural block diagram of a data calling device provided in Embodiment 2 of the present application;

[0015] Figure 6 A schematic diagram of the structure of an electronic device provided in Example 3 of the present application. DETAILED DESCRIPTION

[0016] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the embodiments of the present application should fall within the scope of protection of the embodiments of the present application.

[0017] The specific implementation of the embodiment of the present application is further explained below in conjunction with the accompanying drawings of the embodiment of the present application.

[0018] Embodiment 1

[0019] The first embodiment of the present application provides a data calling method, which is applied to a data calling device. For ease of understanding, the application scenario of the data calling method provided in the first embodiment of the present application is described. Figure 1 As shown, Figure 1 A scenario diagram of a data calling method provided in Example 1 of the present application. Figure 1 The illustrated scenario shows various functional modules of the data calling device, which specifically includes: a first container, a second container, a preset interface, and a page stack manager. It should be noted that these functional modules can be implemented by hardware structures such as a processor and a memory, and the memory can store programs for implementing these functional modules.

[0020] Among them, the first container is used to load the first page, and the second container is used to load the second page. The rules for calling data of the first container and the second container are different; the preset interface is used to implement the preset function, and the preset function depends on the data of the second page, that is, depends on the function of the second container; the page stack manager is used to manage the page stack (including at least the first page and the second page).

[0021] The data calling device can also access the network, connect to the cloud through the network, and exchange data. In this application, the network includes a local area network (LAN), a wide area network (WAN), and a mobile communication network; such as the World Wide Web (WWW), the Long Term Evolution (LTE), the 2G network (2nd Generation Mobile Network), the 3G network (3rd Generation Mobile Network), and the 5G network (5th Generation Mobile Network). Of course, this is only an exemplary description and does not mean that the application is limited to this.

[0022] like Figure 1 As shown, when the first container loads the first page, if the first page needs to call the data of the second page, the preset interface of the first container is registered as the listener of the second page in the page stack manager; the page stack manager is used to jump to the second page, and the second container is used to load the second page. The second container obtains the data of the second page during the process of loading the second page; when the result returned by the second page is monitored by the preset interface, the page stack manager is used to call back the data of the second page to the first container through the preset interface; and the first page is loaded using the data of the first container and the second page.

[0023] Combination Figure 1 The scenario shown in the figure describes in detail the data calling method provided in the first embodiment of the present application. It should be noted that: Figure 1 This is just one application scenario of the data calling method provided in the first embodiment of the present application, and does not mean that the data calling method must be applied to Figure 1 The scene shown, see Figure 2 As shown, Figure 2 A flowchart of a data calling method provided in Embodiment 1 of the present application, the method comprising the following steps:

[0024] Step 201: When a first page is loaded in a first container, if the first page needs to call data of a second page, a preset interface of the first container is registered in a page stack manager as a listener of the second page.

[0025] A container can be a packaged software unit so that an application can run from one computing environment to another computing environment. In the present application, a first container can be used to load a first page, and the first page can be any page. Optionally, the preset function implemented by the preset interface depends on the second container, and the first container cannot implement the preset function. The second container can be used to load the second page, because the first container cannot implement the preset function, and the implementation of the preset function depends on the second container. Therefore, it is necessary to call the second container through the preset interface to implement the preset function and return the data, that is, the first page calls the data of the second page through the preset interface. In one implementation, the preset interface is the interface for the first container to call the data of the second container.

[0026] The page stack manager is used to manage the page stack. The page stack may include multiple pages, and the multiple pages include at least a first page and a second page. Figure 3 As shown, Figure 3 A schematic diagram of a page stack provided for the first embodiment of the present application, in which pages can be inserted and deleted, inserting a page can also be called pushing into the stack, and deleting a page can also be called popping out of the stack. The pages in the page stack can be read and displayed to the user. The page stack manager can manage the page life cycle events of each page in the page stack, and the page life cycle events may include, for example: page loading (onLoad) event, page display (onShow) event, page unloading (onUnload) event, etc. Exemplarily, the page loading (onLoad) event is triggered when the page is first entered and the page is loaded, and the parameters of the open page path can be obtained in the parameters of the page loading event; the page display event is triggered when the background switches to the foreground or re-enters the page after the first loading is completed; the page unloading event is triggered when the page is unloaded. Of course, the page life cycle events may also include other events, such as the return result (onResult) event, etc., which are only exemplary here.

[0027] Optionally, in one embodiment of the present application, because the first page needs to call the data of the second page, it is possible to only listen to the return result event, and register the preset interface of the first container as the listener of the second page in the page stack manager, including: registering the preset interface as the listener of the return result event of the second page in the page manager. Using the preset interface to only listen to the return result event is more efficient, and other events that are not related to calling the data of the second page will not be listened to, which also reduces the power consumption of the listening.

[0028] Step 202: In response to the request to jump to the second page, the page stack manager jumps to the second page and loads the second page using the second container.

[0029] It should be noted that in the present application, the first container and the second container are two types of containers, and the rules for calling data of the first container and the second container are different. Specifically, the upper application may call the container with different data calling rules. Exemplarily, the first container and the second container may be two containers of different types in the container of the mini program, the container of the dynamic interface technology (AJX), the container of the react native (English: React native), the weex container, and the flutter container; for example, the first container may be a container of the mini program, the mini program may be a global wide area network (English: World Wide Web, WEB) application, and the second container may be a container of the dynamic interface technology (AJX) or a dynamic container; or, the first container is an AJX container, and the second container is a container of the mini program. Of course, this is just an exemplary explanation. As long as the first container and the second container meet different rules for calling data, if the calling rules of the first container and the second container are the same, the first container can directly call the data of the second container, that is, in the process of loading the first page, the first container can directly call the data of the second page.

[0030] It should be noted that the use of the page stack manager to jump to the second page can be initiated when the preset interface is registered as the listener of the second page, that is, when the preset interface is registered as the listener of the second page with the page stack manager, a request to jump to the second page is initiated, the page stack manager starts to jump to the second page, and then the second container loads the second page and displays it. The page stack manager jumps to the second page and the second container loads the second page can be executed synchronously. Here, two examples are listed to specifically illustrate the execution actions of the page stack manager and the second container respectively:

[0031] Optionally, in the first example, in response to the request to jump to the second page, the page stack manager jumps to the second page, including: using the unified jump interface of the page stack manager to jump from the current page to the second page, and displaying the second page. It should be noted that the unified jump interface is used for jumping to any page in the page stack. Using a unified jump interface to complete the jump to any page in the page stack is more convenient and more efficient in page management.

[0032] Optionally, in the second example, using the second container to load the second page includes: using the second container to execute the task logic of the second page, and obtaining data of the second page according to the execution result.

[0033] It should be noted that, when the second container executes the task logic of the second page, the second page is gradually loaded and the user can see the second page. Of course, when the page stack manager is used to jump to the second page, the second page is displayed to the user and the second container executes the task logic in the background.

[0034] It should be noted that, during the display of the second page, the user may continue to operate, or the user does not need to operate, to implement the preset function corresponding to the preset interface. After the preset function is implemented, the second container generates data for the second page.

[0035] Step 203: When the preset interface monitors the return result event of the second page, the page stack manager is used to call back the data of the second page to the first container through the preset interface.

[0036] Optionally, the page stack manager can respond to multiple page life cycle event listeners. In one implementation, when the preset interface listens to the return result event of the second page, the page stack manager is used to call back the data of the second page to the first container through the preset interface, including: the page stack manager traverses the page life cycle event listeners, and when the return result event occurs on the second page, the page manager returns the listening result of the return result event of the second page to the preset interface, and the page stack manager calls back the data of the second page from the second container to the first container through the preset interface. The page stack manager traverses the page life cycle event listeners and can respond to multiple listeners, or respond to all listeners, thereby returning the listened results to multiple listeners, and the management efficiency is higher. By using the page stack manager to call back the data of the second page from the second container to the first container through the preset interface, data communication between the first container and the second container can be realized. In the process of realizing the data communication, there is no need to develop a bridge separately, which is more convenient to implement. It can be applied to various scenarios that require communication between containers, with a wider range of applications and better compatibility.

[0037] Step 204: Load the first page using the data of the first container and the second page.

[0038] Optionally, after the page stack manager returns the data of the second page to the first container through a preset interface, it can jump to the first page, and then use the data of the first container and the second page to load the first page. For example, in one implementation, using the data of the first container and the second page to load the first page includes: using the unified jump interface of the page stack manager to jump from the second page to the first page; using the data of the first container and the second page to load the first page, and displaying the first page. It should be noted that the first page can be displayed according to the loading progress.

[0039] Combination Figure 1 Based on the description of steps 201-204 above, another specific scenario is cited here to illustrate the data calling method described in steps 201-204. Figure 4 As shown, Figure 4A scenario diagram of another data calling method provided in the first embodiment of the present application. Here, the first container is a container of a WEB applet, and the second container is an AJX container. Correspondingly, the page can be a WEB applet page, and the second page can be an AJX page. The preset interface can be used to call the data of the second page (AJX page). Figure 4 In the scenario shown, the preset interface can realize the function of selecting pictures. The function of selecting pictures cannot be realized by the WEB applet, but can be realized by the AJX container. Therefore, when realizing the function of selecting pictures, it is necessary to call the data of the AJX page.

[0040] Combination Figure 4 In the scenario shown, the user triggers the function of selecting a picture through an interactive operation on the mini program page. The interactive operation may include touch operation, gesture operation, voice interactive operation, etc. After the data calling device detects the user's interactive operation on the mini program page, the container of the mini program page calls a preset interface to trigger the function of selecting a picture. Specifically, the preset interface initiates a request to the page stack manager to jump to the AJX page, and registers the preset interface in the page stack manager as a listener of the return result event of the AJX page. The page stack manager jumps the currently displayed mini-program page to the AJX page, uses the AJX container to load and render the AJX page, and the data calling device displays the AJX page. The user can complete the operation of selecting a picture on the AJX page. The AJX container generates data for the AJX page based on the user's operation of selecting a picture. The page stack manager traverses the listeners of the page life cycle events. When the AJX container returns the data of the AJX page, the data of the AJX page is called back to the container of the mini-program through the preset interface. The page stack manager jumps the currently displayed AJX page to the mini-program page, the container of the mini-program page loads the mini-program page according to the data of the AJX page, and the data calling device displays the mini-program page to the user.

[0041] The data calling method provided in the embodiment of the present application, when using the first container to load the first page, if the first page needs to call the data of the second page, by registering the preset interface of the first container as the listener of the second page in the page stack manager, so as to use the preset interface to listen to the second page, when the return result event of the second page is listened, the data of the second page can be called back to the first container through the page stack manager and the preset interface, thereby realizing data communication between containers, and registering an interface as the listener of a certain page does not need to be developed separately, so its application range is wider, and it is very convenient to implement, thereby reducing development costs.

[0042] Embodiment 2

[0043] Based on the method described in the above embodiment 1, the second embodiment of the present application provides a data calling device for executing the method described in the above embodiment 1, referring to Figure 5 As shown, the data calling device 50 includes:

[0044] The registration module 501 is used to register the preset interface of the first container as a listener of the second page in the page stack manager when the first page is loaded in the first container and if the first page needs to call the data of the second page;

[0045] The page management module 502 is used for the page stack manager to jump to the second page in response to the request to jump to the second page, and load the second page using the second container;

[0046] The monitoring module 503 is used to use the page stack manager to call back the data of the second page to the first container through the preset interface when the preset interface monitors the return result event of the second page;

[0047] The page management module 502 is further configured to load the first page using the data of the first container and the second page.

[0048] Optionally, in one embodiment of the present application, the monitoring module 503 is used for the page stack manager to traverse the page life cycle event listeners. When a return result event occurs on the second page, the page stack manager calls back the data of the second page from the second container to the first container through a preset interface.

[0049] Optionally, in one embodiment of the present application, the page management module 502 is used to execute the task logic of the second page using the second container, and obtain the data of the second page according to the execution result.

[0050] Optionally, in one embodiment of the present application, the page management module 502 is used to jump from the current page to the second page and display the second page by using the unified jump interface of the page stack manager.

[0051] Optionally, in one embodiment of the present application, the page management module 502 is used to jump from the second page to the first page using the unified jump interface of the page stack manager; load the first page using the data of the first container and the second page, and display the first page.

[0052] Optionally, in one embodiment of the present application, the registration module 501 is used to register the preset interface in the page manager as a listener of the return result event of the second page.

[0053] The data calling device provided in the embodiment of the present application, when using the first container to load the first page, if the first page needs to call the data of the second page, by registering the preset interface of the first container as the listener of the second page in the page stack manager, the second page is listened to using the preset interface, and when the return result event of the second page is listened to, the data of the second page can be called back to the first container through the page stack manager and the preset interface, thereby realizing data communication between containers. Registering an interface as the listener of a certain page does not need to be developed separately, so its application range is wider, and it is very convenient to implement, thereby reducing development costs.

[0054] Embodiment 3

[0055] Based on the method described in the above embodiment 1, the third embodiment of the present application provides an electronic device for executing the method described in the above embodiment 1, referring to Figure 6 As shown, Figure 6 This is a schematic diagram of the structure of an electronic device provided in Example 3 of the present application. The specific embodiments of the present application do not limit the specific implementation of the electronic device.

[0056] like Figure 6 As shown, the electronic device may include: a processor (processor) 602 , a communication interface (Communications Interface) 604 , a memory (memory) 606 , and a communication bus 608 .

[0057] in:

[0058] The processor 602 , the communication interface 604 , and the memory 606 communicate with each other via a communication bus 608 .

[0059] The communication interface 604 is used to communicate with other electronic devices such as terminal devices or servers.

[0060] The processor 602 is used to execute the program 610, and specifically can execute the relevant steps in the above method embodiment.

[0061] Specifically, the program 610 may include program codes, which include computer operation instructions.

[0062] The processor 602 may be a processor CPU, or an application specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the electronic device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0063] The memory 606 is used to store the program 610. The memory 606 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0064] The program 610 can be specifically used to enable the processor 602 to execute any method in the aforementioned embodiment 1.

[0065] The specific implementation of each step in program 610 can refer to the corresponding description of the corresponding steps and units in the above data calling method embodiment, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described devices and modules can refer to the corresponding process description in the above-mentioned method embodiment, which will not be repeated here.

[0066] The electronic device provided by the embodiment of the present application, when using the first container to load the first page, if the first page needs to call the data of the second page, by registering the preset interface of the first container as the listener of the second page in the page stack manager, the second page is listened to using the preset interface, and when the return result event of the second page is listened to, the data of the second page can be called back to the first container through the page stack manager and the preset interface, thereby realizing data communication between containers, and registering an interface as the listener of a certain page does not need to be developed separately, its application range is wider, and it is very convenient to implement, thereby reducing development costs.

[0067] Embodiment 4

[0068] Based on the method described in the above-mentioned embodiment 1, embodiment 4 of the present application provides a computer storage medium, on which a computer program is stored, and when the program is executed by a processor, the method described in embodiment 1 is implemented.

[0069] The computer storage medium provided in the embodiment of the present application, when using the first container to load the first page, if the first page needs to call the data of the second page, by registering the preset interface of the first container as the listener of the second page in the page stack manager, the second page is listened to using the preset interface, and when the return result event of the second page is listened to, the data of the second page can be called back to the first container through the page stack manager and the preset interface, thereby realizing data communication between containers, and registering an interface as the listener of a certain page does not need to be developed separately, so its application range is wider, and it is very convenient to implement, thereby reducing development costs.

[0070] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0071] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as a computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a special-purpose processor or programmable or special-purpose hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the data call method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the data call method shown here, the execution of the code converts the general-purpose computer into a special-purpose computer for executing the data call method shown here.

[0072] Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0073] The above implementation methods are only used to illustrate the embodiments of the present application, and are not limitations on the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also belong to the scope of the embodiments of the present application. The scope of patent protection of the embodiments of the present application should be limited by the claims.

Claims

1. A data calling method, comprising: When the first container loads the first page, if the first page needs to call the data of the second page, the preset interface of the first container is registered in the page stack manager as the listener of the second page; The page stack manager jumps to the second page in response to the request to jump to the second page, and loads the second page using a second container; When the preset interface monitors the return result event of the second page, the page stack manager is used to call back the data of the second page to the first container through the preset interface; The first page is loaded using the data of the first container and the second page.

2. The method according to claim 1, wherein: When the preset interface monitors the return result event of the second page, calling back the data of the second page to the first container through the preset interface by using the page stack manager includes: The page stack manager traverses the page lifecycle event listeners. When a return result event occurs on the second page, the page stack manager returns the listening result of the return result event of the second page to the preset interface. The page stack manager calls back the data of the second page from the second container to the first container through the preset interface.

3. The method according to claim 1, wherein: The using the second container to load the second page includes: The task logic of the second page is executed by using the second container, and the data of the second page is obtained according to the execution result.

4. The method according to claim 1, wherein: The page stack manager jumps to the second page in response to the request to jump to the second page, including: Using the unified jump interface of the page stack manager, jump from the current page to the second page, and display the second page.

5. The method according to claim 1, wherein: The step of loading the first page by using the data of the first container and the second page includes: Using the unified jump interface of the page stack manager, jumping from the second page to the first page; The first page is loaded using the data of the first container and the second page, and the first page is displayed.

6. The method according to claim 1, wherein: The step of registering the preset interface of the first container as a listener of the second page in the page stack manager includes: The preset interface is registered in the page stack manager as a listener of the return result event of the second page.

7. A data calling device, comprising: A registration module, used for registering a preset interface of the first container as a listener of the second page in the page stack manager when the first page is loaded in the first container, if the first page needs to call data of the second page; a page management module, configured for the page stack manager to jump to the second page in response to a request to jump to the second page, and to load the second page using a second container; A monitoring module, configured to, when the preset interface monitors a return result event of the second page, use a page stack manager to call back the data of the second page to the first container through the preset interface; The page management module is used to load the first page using the data of the first container and the second page.

8. An electronic device comprising: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform an operation corresponding to the data calling method according to any one of claims 1-6.

9. A computer storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the data calling method according to any one of claims 1 to 6 is implemented.

Images