A bridging method and device
By generating a manager and establishing a connection relationship, the web page side can realize direct call to the local ends of different operating platforms, solving the problem of inefficient bridging adjustment and utilization in the existing technology, and improving the development efficiency of hybrid applications.
Patent Information
- Application Number
- CN202110192049.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-02-19
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-02-19
AI Technical Summary
In the prior art, the bridging between the web page end and the local ends of different operating platforms is difficult to uniformly adjust and directly utilize, resulting in low development efficiency.
By receiving call requests from the web page, obtaining the bridge object and call content, generating a manager, and establishing a connection relationship between the manager and the target end, sending corresponding call functions to instruct the target end to execute the call content, realizing the web page to the local side of the different operating platforms Call directly.
It improves the development efficiency of hybrid applications and reduces the workload, so that the web page can directly call the local functions of different operating platforms.
Smart Images

Figure CN112925658B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a bridging method and device. Background Art
[0002] During the operation of hybrid apps, the web view needs to be bridged with the native view of different operating platforms to obtain the underlying capability support, audio and video rendering or hardware control in the native view.
[0003] In the prior art, the bridging between the web page and the local end generally has the following problems: when calling the local end of different operating platforms, it is necessary to bridge with the corresponding local end respectively. This decentralized bridging is difficult to be uniformly adjusted or directly used when developing new projects. Summary of the invention
[0004] In view of this, an embodiment of the present invention provides a bridging method and device so that the bridging with the local ends of different operating platforms can be uniformly adjusted or directly utilized.
[0005] In a first aspect, an embodiment of the present invention provides a bridging method, the method comprising:
[0006] Receive the call request sent by the web page;
[0007] Obtaining a bridge object and a call content corresponding to the call request;
[0008] Generate a manager according to the calling content and the bridge object;
[0009] Establishing a connection relationship between the manager and the target end;
[0010] A calling function corresponding to the calling content is sent to the target end through the manager.
[0011] Furthermore, the establishing of the connection relationship between the manager and the target end specifically includes:
[0012] The manager sends an interface identifier to the target end; the interface identifier is used to indicate a registration interface of the target end.
[0013] Furthermore, after obtaining the bridge object and the call content corresponding to the call request, the method further includes:
[0014] Obtain a calling function corresponding to the bridge object and the calling content; wherein the calling function is used to instruct the target end to execute the calling content.
[0015] Furthermore, the target end is a local end of a different operating platform.
[0016] Furthermore, the bridge object is an operating platform corresponding to the target end.
[0017] Furthermore, the calling content includes a calling function and a calling operation; wherein the calling function is an accessible function provided by the target end.
[0018] Furthermore, after receiving the call request sent by the web page, the method further includes:
[0019] Obtain interface information corresponding to the call request and register the interface.
[0020] Furthermore, after sending the calling function corresponding to the calling content to the target end through the manager, the method further includes:
[0021] Receiving feedback information sent by the target end;
[0022] Sending dispatch information to the web page end through the event dispatch end;
[0023] The dispatch information is reply information made in response to the call request.
[0024] Furthermore, after the event dispatching end sends the dispatching information to the webpage end, the method further includes:
[0025] In response to receiving the decoupling information sent by the web page, the interface with the web page is deregistered through the SDK loader.
[0026] In a second aspect, an embodiment of the present invention provides an electronic device, comprising a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method described in the first aspect.
[0027] In a third aspect, an embodiment of the present invention provides a computer-readable storage medium for storing computer program instructions, wherein the computer program instructions implement the method described in the first aspect when executed by a processor.
[0028] The embodiment of the present invention discloses a bridging method and device. The bridging method obtains a bridging object and a calling content corresponding to the calling request after receiving a calling request sent by a web page, generates a new manager, establishes a connection relationship between the newly generated manager and a target end, and sends a calling function corresponding to the calling content to the target end through the manager to instruct the target end to execute the calling content, so that the web page end can directly send a calling request to call a local end of a different operating platform, thereby improving the development efficiency of hybrid applications. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] The above and other objects, features and advantages of the present invention will become more apparent through the following description of the embodiments of the present invention with reference to the accompanying drawings, in which:
[0030] Figure 1 is a flow chart of a bridging method according to an embodiment of the present invention;
[0031] Figure 2 A system signaling diagram of a bridging method according to an embodiment of the present invention;
[0032] Figure 3 A schematic diagram of a flow chart of an optional bridging method according to an embodiment of the present invention;
[0033] Figure 4 A system signaling diagram of an optional bridging method according to an embodiment of the present invention;
[0034] Figure 5 A structural diagram of a generation manager provided in an embodiment of the present invention;
[0035] Figure 6 A schematic diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0036] The present invention is described below based on embodiments, but the present invention is not limited to these embodiments. In the detailed description of the present invention below, some specific details are described in detail. It is possible for a person skilled in the art to fully understand the present invention without the description of these details. In order to avoid confusing the essence of the present invention, known methods, processes, flows, components and circuits are not described in detail.
[0037] In addition, persons of ordinary skill in the art will appreciate that the drawings provided herein are for illustration purposes and are not necessarily drawn to scale.
[0038] Unless the context clearly requires otherwise, words such as “include”, “including” and the like in the specification should be interpreted as including rather than being exclusive or exhaustive; that is, as meaning “including but not limited to”.
[0039] In the description of the present invention, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, "plurality" means two or more.
[0040] In this article, hybrid APP refers to a hybrid application that is half native and half web, which has both the advantages of "good user interaction experience of native apps" and "advantages of cross-platform development of web apps".
[0041] The Hybrid APP used in this article is mainly a web-based type, that is, the main body of the mobile application is the web view, which is mainly written in web language and interspersed with native functions.
[0042] Figure 1 FIG. 1 is a flow chart of a bridging method according to an embodiment of the present invention. Figure 1 As shown, the bridging method of this embodiment includes the following steps:
[0043] In step S101, a call request sent by a web page is received.
[0044] The web page is a web view in a hybrid app. Specifically, when the web view needs to call a function of the native app, it sends a call request to the project entity.
[0045] In this embodiment, the project entity is an npm (Node package manager) Javascript package exposed to the outside as a unified Class, which is an SDK (Software Development Kit) Class in this example.
[0046] The call request may be issued by a script program written in Javascript language on the web page in response to a specific operation or trigger condition. Specifically, the call request includes a bridge object and call content.
[0047] In step S102, a bridge object and a calling content corresponding to the calling request are obtained.
[0048] The bridge object is the operating platform corresponding to the local end to be called. Optionally, the operating platform can be IOS, Android, Linux or Windows.
[0049] The calling content includes a calling operation and a calling function corresponding to the calling operation.
[0050] The calling function refers to an accessible function provided by the local end to the outside. Optionally, the access function can be underlying capability support, video function, audio function or signal function.
[0051] Specifically, after receiving the call request sent by the web page, the bridge object corresponding to the call request, the call operation, and the call function corresponding to the call operation are obtained. For example, when the web page needs to create a video window on the local side of the IOS platform, a call request containing IOS, video window creation, and video function information is sent to the SDK. After receiving the call request, the SDK will obtain the relevant information in the call request.
[0052] Optionally, the call request may also include relevant parameters required for the call operation.
[0053] In step S103, a manager is generated according to the calling content and the bridge object.
[0054] Specifically, according to the bridge object and the calling function corresponding to the calling operation, a corresponding manager is generated. The manager is essentially an executable program instance. For example, if the information obtained is that the bridge object is IOS and the calling function is a video function, a video manager with the bridge object being IOS will be generated.
[0055] Optionally, for different bridge objects and call contents, the manager may also obtain a device manager, obtain an audio manager, or obtain a signaling manager.
[0056] In step S104, a connection relationship between the manager and the target end is established.
[0057] The target end is the local end of the called operating platform.
[0058] Specifically, after the new manager is generated, a connection relationship between the newly generated manager and the local end is established. After the connection relationship is established, the manager can send information to the target end through the connection relationship.
[0059] Optionally, the manager establishes contact with the local end by sending an interface identifier to the target end through the newly generated manager, where the interface identifier is used to indicate a registration interface of the target end.
[0060] In step S105, a calling function corresponding to the calling content is sent to the target end through the manager.
[0061] The calling function corresponds to the calling content and the bridge object, and is used to instruct the target end to execute the calling content.
[0062] Specifically, through the newly generated connection relationship, the manager sends a call function to the target end for instructing the target end to execute the call content. For example, the SDK can obtain the video manager and send a call function to the local end of the IOS platform for instructing the local end to execute the creation of a video window.
[0063] Optionally, if a corresponding manager that has been generated is obtained when the manager is generated according to the bridge object and the calling content, the calling function is directly sent to the target end through the manager.
[0064] Optionally, the calling function may be preset and stored in a memory.
[0065] Optionally, the calling function pre-set in the memory can be read according to actual needs. In an optional implementation, after obtaining the bridge object and the calling content corresponding to the calling request, the calling function corresponding to the bridge object and the calling content can be read from the memory at the same time. The calling function is used to instruct the target end to execute the calling content.
[0066] Optionally, when reading the calling function, the corresponding calling function may be found from the memory according to the calling content and the bridge object.
[0067] After receiving a call request sent by a web page, the embodiment of the present invention obtains a bridge object and call content corresponding to the call request, generates a new manager, establishes a connection relationship between the newly generated manager and the target end, and sends a call function corresponding to the call content to the target end through the manager to instruct the target end to execute the call content. After obtaining the bridge object and the call content, the embodiment of the present invention generates a corresponding manager to establish a connection relationship with different target ends, so that the web page can call the local end of different operating platforms by directly sending a call request, which reduces the workload and improves the development efficiency.
[0068] Figure 2 FIG. 1 is a system signaling diagram of the bridging method according to an embodiment of the present invention. Figure 2 As shown, the system includes a web page end, a project entity and a target end. The web page end and the target end are the web page end and the local end in the hybrid mode application.
[0069] The project entity is an npm (Node package manager) Javascript package that is exposed as a unified Class, which in this case is an SDK (Software Development Kit) Class.
[0070] As shown in step S201, when the web page needs to mobilize the function support of the local side, it needs to send a call request to the SDK.
[0071] Optionally, the call request can be issued by a script program written in Javascript in response to a specific operation or trigger condition. Specifically, the call request includes a bridge object and a call content. For example, if the web page needs to mobilize the local mobile form of the IOS platform, it needs to send a call request containing IOS, video function and mobile form information to the SDK.
[0072] As shown in step S202, after the SDK receives the call request, it obtains the bridge object and the call content from the call request.
[0073] Among them, the bridge object is the operating platform corresponding to the local end that needs to be called. Optionally, the operating platform can be IOS, Android, Linux or Windows. The calling content includes the calling operation and the corresponding calling function. The calling function refers to the accessible function provided by the local end to the outside. Optionally, the access function can be the underlying capability support, video function, audio function or signal function. For example: After receiving the calling request, the SDK will obtain the relevant information of IOS, video function and mobile window in the calling request.
[0074] Optionally, the calling request may also include parameters related to the calling operation, such as the number of windows to be created and parameters related to moving windows.
[0075] As shown in step 203, the SDK generates a manager based on the acquired bridge object and the calling content.
[0076] The manager is essentially an executable program instance. Figure 5 The structure diagram of the generation manager provided in the embodiment of the present invention is as follows: Figure 5 As shown in the figure, the SDK will generate different managers according to different bridge objects and bridge contents. For example, when the SDK obtains information about IOS, video functions, and mobile forms, it will generate a video manager with the bridge object being IOS.
[0077] Optionally, for different bridge objects and calling contents, the manager may also obtain a device manager, obtain an audio manager, or obtain a signaling manager.
[0078] As shown in step 204, after the SDK generates the corresponding manager, the manager sends an interface identifier to the target end, wherein the interface identifier contains relevant information for instructing the target end to register the interface. The target end is the local end of the called operating platform.
[0079] As shown in step 205, after the target end obtains the interface identifier, it obtains the interface information in the interface identifier, and registers and generates a new interface according to the interface information, and establishes a connection relationship between the SDK and the target end through the interface.
[0080] As shown in step 206, after the connection relationship is established, the manager can send a call function to the target end through the connection relationship.
[0081] The calling function corresponds to the calling content and the bridge object, and is used to instruct the target end to execute the calling content. For example, the video manager obtains the calling function for instructing the target end to execute the mobile window through the connection relationship to the local end of the IOS platform.
[0082] Optionally, if a corresponding manager that has been generated is obtained when the manager is generated according to the bridge object and the calling content, the calling function is directly sent to the target end through the manager.
[0083] Optionally, the calling function may be pre-set and stored in memory.
[0084] Optionally, the calling function pre-set in the memory can be read according to actual needs. In an optional implementation, after obtaining the bridge object and the calling content corresponding to the calling request, the calling function corresponding to the bridge object and the calling content can be read from the memory at the same time. The calling function is used to instruct the target end to execute the calling content.
[0085] Optionally, when reading the calling function, the corresponding calling function may be read from the memory according to the calling content and the bridge object.
[0086] As shown in step 207, after receiving the calling function, the target end executes the calling content according to the calling function.
[0087] After receiving a call request sent by a web page, the embodiment of the present invention obtains a bridge object and call content corresponding to the call request, generates a new manager, establishes a connection relationship between the newly generated manager and the target end, and sends a call function corresponding to the call content to the target end through the manager to instruct the target end to execute the call content. After obtaining the bridge object and the call content, the embodiment of the present invention generates a corresponding manager to establish a connection relationship with different target ends, so that the web page can call the local end of different operating platforms by directly sending a call request, which reduces the workload and improves the development efficiency.
[0088] Figure 3 FIG. 1 is a flow chart of an optional bridging method according to an embodiment of the present invention. Figure 3 As shown, the method comprises the following steps:
[0089] S301: Receive a call request sent by a web page.
[0090] S302: Obtain interface information corresponding to the call request and register the interface.
[0091] S303: Acquire the bridge object and calling content corresponding to the calling request.
[0092] S204: Generate a manager according to the calling content and the bridge object.
[0093] S305: The manager sends an interface identifier to the target end.
[0094] S306: Sending a calling function corresponding to the calling content to the target end through the manager.
[0095] S307: Receive feedback information sent by the target end.
[0096] S308: Sending dispatch information to the web page via the event dispatching end.
[0097] S309: In response to receiving the decoupling information sent by the web page, canceling the interface with the web page through the SDK loader.
[0098] S301 and S303-S306 in the above steps can refer to the above Figure 1 The description shown is not repeated here.
[0099] For step S302, specifically, the interface information corresponding to the call request sent by the web page is obtained, and the interface is registered to establish a connection relationship with the web page. After the connection relationship is established, the call request sent by the web page is received through the connection relationship.
[0100] For step S307, specifically, feedback information sent by the target end is received, where the feedback information is feedback information from the target end regarding the call content.
[0101] Optionally, the feedback information may include information on whether the target end successfully executes the call content and the execution time. If the call content is not successfully executed, it may also include information such as an error code and other parameter information involved in the execution process. For example, when the target end receives a call function corresponding to the call content and executes the call content and an error occurs, the execution time or error time is recorded and the obtained error code is fed back as feedback information.
[0102] For step S308, specifically, a dispatching message is sent to the web page end through the event dispatching end, and the dispatching message is reply information for the call request sent by the web page end.
[0103] Optionally, the reply information can be determined based on the feedback information returned by the target end, and can include information on whether the target end successfully executes the call content and the execution time. If the call content is not executed, it can also include information such as an error code and other parameter information involved in the execution process.
[0104] Optionally, different managers use a unified event dispatching end to send reply information to the web page end.
[0105] Optionally, the dispatched information is reply information for the call request sent by the web page, rather than sending information directly to the web page, so that the developer can directly view the reply information made for the call request without missing any information.
[0106] For step S309, specifically, in response to receiving the decoupling information sent by the web page, the SDK loader cancels the interface between the web page and the web page to disconnect the connection relationship with the web page.
[0107] Optionally, if the call request sent by the web page is not received within a preset time, the interface with the web page is automatically logged out to disconnect the connection with the web page. The preset time can be set by the developer according to actual needs, for example, the preset time can be the maintenance or update cycle time of the SDK.
[0108] Optionally, the SDK loader can also be used to maintain and update the SDK.
[0109] After receiving the call request from the web page, the embodiment of the present invention establishes a connection relationship with the web page, and then Figure 1 Based on the method shown, feedback information made by the target end in response to the call content is received, and a reply message is sent to the web page end through the event dispatch end. In response to receiving the decoupling information sent by the web page end, the SDK loader deregisters the interface between the web page end, and reloads the SDK and connects when a call is required. In this way, when there is no call demand, the memory usage is reduced by deregistering the interface, ensuring the self-maintenance and update of the SDK, reducing the workload of the staff and improving the development efficiency of the developers.
[0110] Figure 4 FIG. 1 is a system signaling diagram of an optional bridging method according to an embodiment of the present invention. Figure 4 As shown, the system includes a web page, a project entity and a target end. The project entity is an npm (Node package manager) Javascript package exposed as a unified Class, which is an SDK (Software Development Kit) Class in this example.
[0111] Steps S401 and S403-S407 can be found in the above Figure 2 The description shown is not repeated here.
[0112] For step S402, specifically, the SDK obtains the interface information corresponding to the call request sent by the web page, and registers the interface to establish a connection relationship with the web page. After the connection relationship is established, the call request sent by the web page is received through the connection relationship.
[0113] Regarding step S408, after executing the calling content according to the calling function, the target end sends feedback information to the SDK, where the feedback information is feedback information of the target end for the calling content.
[0114] Optionally, the feedback information may include information on whether the target end successfully executes the call content and the execution time. If the call content is not successfully executed, it may also include information such as an error code and other parameter information involved in the execution process. For example, when the target end receives a call function corresponding to the call content and executes the call content and an error occurs, the execution time or error time is recorded and the obtained error code is fed back to the SDK as feedback information.
[0115] For step S409, specifically, the dispatch information is sent to the web page end through the event dispatch end in the SDK.
[0116] Optionally, the reply information can be determined based on the feedback information returned by the target end, and can include information on whether the target end successfully executes the call content and the execution time. If the call content is not executed, it can also include information such as an error code and other parameter information involved in the execution process.
[0117] Optionally, different managers generated by the SDK use a unified event dispatching end to send reply information to the web page end.
[0118] Optionally, the dispatched information is reply information for the call request sent by the web page, rather than sending information directly to the web page, so that the developer can directly view the reply information made by the SDK for the call request without missing any information.
[0119] For step S410, specifically, in response to receiving the decoupling information sent by the web page, the SDK disconnects the connection with the web page by deregistering the interface between the SDK loader and the web page.
[0120] Optionally, if the call request sent by the web page is not received within a preset time, the interface with the web page is automatically logged out to disconnect the connection with the web page. The preset time can be set by the developer according to actual needs, for example, the preset time can be the maintenance or update cycle time of the SDK.
[0121] For step S411, the SDK cancels the interface with the web page through the SDK loader.
[0122] Optionally, the SDK loader may deregister the interface by sending a deregistration mark to the SDK, wherein the deregistration mark includes the decoupling information and the interface information of the interface to be deregistered.
[0123] Optionally, the SDK loader can also be used to maintain and update the SDK.
[0124] After receiving the call request from the web page, the embodiment of the present invention establishes a connection relationship with the web page, and then Figure 1 Based on the method shown, feedback information made by the target end in response to the call content is received, and a reply message is sent to the web page end through the event dispatch end. In response to receiving the decoupling information sent by the web page end, the SDK loader deregisters the interface between the web page end, and reloads the SDK and connects when a call is required. In this way, when there is no call demand, the memory usage is reduced by deregistering the interface, ensuring the self-maintenance and update of the SDK, reducing the workload of the staff and improving the development efficiency of the developers.
[0125] Figure 6 Schematic diagram of an electronic device according to an embodiment of the present invention. Figure 6 As shown, the electronic device is a general data processing device, which includes a general computer hardware structure, which at least includes a processor 61 and a memory 62. The processor 61 and the memory 62 are connected via a bus 63. The memory 62 is suitable for storing instructions or programs executable by the processor 61. The processor 61 can be an independent microprocessor or a collection of one or more microprocessors. Thus, the processor 61 executes the instructions stored in the memory 62, thereby executing the method flow of the embodiment of the present invention as described above to realize the processing of data and the control of other devices. The bus 63 connects the above-mentioned multiple components together, and at the same time connects the above-mentioned components to the display controller 64 and the display device and the input / output (I / O) device 65. The input / output (I / O) device 65 can be a mouse, a keyboard, a modem, a network interface, a touch input device, a somatosensory input device, a printer, and other devices known in the art. Typically, the input / output device 65 is connected to the system via an input / output (I / O) controller 66.
[0126] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices (equipment) or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may adopt a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0127] The present application is described with reference to flowcharts of methods, apparatuses (devices) and computer program products according to embodiments of the present application. It should be understood that each process in the flowchart can be implemented by computer program instructions.
[0128] These computer program instructions may be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device that implements the process Figure 1 A function specified in a process or multiple processes.
[0129] These computer program instructions may also be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce the instructions for implementing the process Figure 1 A device that specifies functions in a process or multiple processes.
[0130] Another embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program, wherein the computer-readable program is used for a computer to execute part or all of the above method embodiments.
[0131] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by specifying relevant hardware through a program, and the program is stored in a storage medium, including several instructions for a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0132] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A bridging method, characterized in that: The method comprises: Receive the call request sent by the web page; Obtaining a bridge object and a call content corresponding to the call request; Generate a manager according to the calling content and the bridge object; Establishing a connection relationship between the manager and the target end; A calling function corresponding to the calling content is sent to the target end through the manager, wherein the manager is a program instance configured to manage all calling processes corresponding to the calling function within a life cycle, and the life cycle of the manager lasts until the decoupling information sent by the web page is received.
2. The method according to claim 1, characterized in that: The establishing of a connection relationship between the manager and the target end specifically includes: The manager sends an interface identifier to the target end; the interface identifier is used to indicate a registration interface of the target end.
3. The method according to claim 1, characterized in that After obtaining the bridge object and the call content corresponding to the call request, the method further includes: Obtain a calling function corresponding to the bridge object and the calling content; wherein the calling function is used to instruct the target end to execute the calling content.
4. The method according to claim 1, characterized in that: The target end is a local end of a different operating platform.
5. The method according to claim 4, characterized in that The bridge object is the operating platform corresponding to the target end.
6. The method according to claim 1, characterized in that The calling content includes calling function and calling operation; The calling function is an accessible function provided by the target end.
7. The method according to claim 1, characterized in that After receiving the call request sent by the web page, the method further includes: Obtain interface information corresponding to the call request and register the interface.
8. The method according to claim 7, characterized in that After sending the calling function corresponding to the calling content to the target end through the manager, the method further includes: Receiving feedback information sent by the target end; Sending dispatch information to the web page end through the event dispatch end; The dispatch information is reply information made in response to the call request.
9. The method according to claim 8, characterized in that After sending the dispatch information to the web page through the event dispatching end, the method further includes: When the manager life cycle ends, the interface with the web page is deregistered through the SDK loader.
10. An electronic device comprising a memory and a processor, characterized in that: The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method according to any one of claims 1 to 9.
11. A computer-readable storage medium for storing computer program instructions, characterized in that: The computer program instructions, when executed by a processor, implement the method according to any one of claims 1 to 9.
