Page interaction method and device, medium, electronic equipment and program product

Abstract

The invention belongs to the technical field of computers, and particularly relates to a page interaction method, a page interaction device, a computer readable medium, electronic equipment and a computer program product. The method comprises the steps that first attribute data is written into a first data channel according to an interaction event triggered on an interaction interface, the first data channel is used for transmitting data between different data processing links, and the first attribute data is used for representing attribute change information generated by the interaction interface in an initiation link of the interaction event; sending a data acquisition request to a data source, wherein the data acquisition request is used for requesting to acquire data responding to the first attribute data; when second attribute data corresponding to the data acquisition request appears in the first data channel, page content displayed on the interactive interface is updated according to the second attribute data, and the second attribute data is used for representing attribute change information generated by the interactive interface in a response link of the interactive event. The interaction efficiency of the application program can be improved.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and specifically relates to a page interaction method, a page interaction device, a computer-readable medium, an electronic device, and a computer program product. Background Art

[0002] With the rapid development of mobile device technology, mobile applications have become an indispensable part of daily life and business activities, and the popularity of these applications has driven the demand for more advanced functions and richer user experience.

[0003] To meet these requirements, developers must integrate a variety of functional modules into mobile applications. Each newly added functional module needs to be designed through software architecture to ensure its compatibility with existing systems and performance optimization. This usually involves using modular design principles so that each functional module can be independently developed, tested, and maintained. In addition, to improve the scalability and maintainability of the application, developers may adopt a microservice architecture to decompose the application into a set of small, loosely coupled services, each of which implements a specific business function.

[0004] As the number of functional modules increases, user interface and user experience design become more critical. In order to manage the complexity of page interactions, developers need to adopt responsive design and adaptive layout to ensure that the application provides a consistent user experience on different devices and screen sizes. To further optimize user interaction, developers may also integrate advanced interaction technologies such as gesture recognition, voice control, and tactile feedback.

[0005] As the functional modules of applications become increasingly diverse and complex, how to simplify the interaction process of applications and improve interaction efficiency is a problem that needs to be solved urgently. Summary of the invention

[0006] The purpose of this application is to provide a page interaction method, a page interaction device, a computer-readable medium, an electronic device and a computer program product, thereby improving the interaction efficiency of the application to a certain extent.

[0007] According to one aspect of an embodiment of the present application, a page interaction method is provided, the method comprising: writing first attribute data into a first data channel according to an interaction event triggered on an interaction interface, the interaction event comprising multiple data processing links, the first data channel being used to transfer data between different data processing links, the first attribute data being used to represent attribute change information generated by the interaction interface in the initiation link of the interaction event; sending a data acquisition request to a data source, the data acquisition request being used to request data that responds to the first attribute data; when second attribute data corresponding to the data acquisition request appears in the first data channel, updating the page content displayed on the interaction interface according to the second attribute data, the second attribute data being used to represent attribute change information generated by the interaction interface in the response link of the interaction event.

[0008] According to one aspect of an embodiment of the present application, a page interaction device is provided, the device comprising:

[0009] a writing module, configured to write first attribute data into a first data channel according to an interaction event triggered on the interaction interface, wherein the interaction event includes a plurality of data processing links, the first data channel is used to transfer data between different data processing links, and the first attribute data is used to represent attribute change information generated by the interaction interface during the initiation link of the interaction event;

[0010] a sending module, configured to send a data acquisition request to a data source, wherein the data acquisition request is used to request to acquire data that responds to the first attribute data;

[0011] The update module is configured to update the page content displayed on the interactive interface according to the second attribute data when the second attribute data corresponding to the data acquisition request appears in the first data channel, and the second attribute data is used to represent the attribute change information generated by the interactive interface in the response phase of the interactive event.

[0012] In some embodiments of the present application, based on the above technical solution, the interaction event includes a page jump event from a first page to a second page; and the update module includes:

[0013] A parsing module, configured to parse the second attribute data to obtain a navigation link of the second page;

[0014] The acquisition module is configured to acquire page configuration data of the second page according to the navigation link, wherein the page configuration data is used to represent page display content and page display effect of the second page;

[0015] The first display module is configured to display the second page on the interactive interface according to the page configuration data.

[0016] In some embodiments of the present application, based on the above technical solution, the acquisition module further includes:

[0017] an initial acquisition module, configured to acquire initial page data of the second page according to the navigation link, wherein the initial page data includes data for initializing configuration of the second page;

[0018] A first acquisition module is configured to acquire first page shared data, where the first page shared data includes data shared from the first page to the second page;

[0019] A first writing module is configured to write the first page shared data into a second data channel, where the second data channel is used to transfer data between different pages;

[0020] The first fusion module is configured to fuse the initial page data with the first page shared data according to the fusion instruction to obtain page configuration data of the second page when a fusion instruction corresponding to the first page shared data appears in the second data channel.

[0021] In some embodiments of the present application, based on the above technical solution, the interaction event also includes a page return event in which the second page returns to the first page; and the update module also includes:

[0022] A second collection module is configured to collect second page shared data, where the second page shared data includes page data shared by the second page to the first page;

[0023] A second writing module is configured to write the second page shared data into the second data channel;

[0024] a second fusion module, configured to, when a fusion instruction corresponding to the second page shared data appears in the second data channel, fuse the second page shared data with the initial page data of the first page according to the fusion instruction to obtain page update data of the first page;

[0025] The second display module is configured to display the first page on the interactive interface according to the page update data of the first page.

[0026] In some embodiments of the present application, based on the above technical solution, the first display module further includes:

[0027] A view creation module is configured to create a second view controller, where the second view controller is used to manage the display process of the second page;

[0028] A view push module, configured to push the second view controller to the top of a navigation stack, where the navigation stack is used to manage a page hierarchy displayed on the interactive interface;

[0029] The view display module is configured to display the second page on the interactive interface according to the second view controller and the page configuration data.

[0030] In some embodiments of the present application, based on the above technical solution, the interaction event also includes a page return event in which the second page returns to the first page; and the second display module further includes:

[0031] A view removal module is configured to remove the second view controller from the top of the navigation stack to obtain a first view controller located below the second view controller, wherein the first view controller is used to manage the display process of the first page;

[0032] The view update module is configured to display the first page on the interactive interface according to the page update data of the first view controller and the first page.

[0033] In some embodiments of the present application, based on the above technical solution, the page interaction device further includes:

[0034] A first function calling module is configured to call and execute an observer registration function of the first data channel, wherein the observer registration function is used to register the attribute object held by the first data channel as an observer, and the observer is used to send a notification to the observer when the attribute changes;

[0035] The second function calling module is configured to call and execute the observer callback function when the attribute of the observed object changes, and the observer callback function is used to trigger a notification to the observer and obtain the attribute change information of the observed object according to the notification.

[0036] In some embodiments of the present application, based on the above technical solution, the observer registration function includes the following fields:

[0037] The key value path is used to indicate the property object registered as the observer;

[0038] Observation options, used to indicate the content of the notification sent by the observed object when the attribute changes;

[0039] The context parameter is used to pass an identifier to the observer callback function, where the identifier is used to distinguish different attribute parameters of the observed object.

[0040] In some embodiments of the present application, based on the above technical solution, the page interaction device further includes:

[0041] The third function calling module is configured to call and execute an observer removal function of the first data channel, where the observer removal function is used to cancel an observer registration operation for the first data channel.

[0042] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the page interaction method in the above technical solution is implemented.

[0043] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the executable instructions to implement a page interaction method as in the above technical solution.

[0044] According to one aspect of an embodiment of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the page interaction method in the above technical solution is implemented.

[0045] In the technical solution provided in the embodiment of the present application, when the user operates on the interactive interface to generate interactive events, the system captures the attribute change information generated by these operations and writes this information into the first data channel as the first attribute data. According to the first attribute data, a data acquisition request can be sent to the data source to request data that can respond to these attribute changes. When the first data channel receives the second attribute data corresponding to the data acquisition request, the page content displayed on the interactive interface can be updated according to the second attribute data. It can be seen that the first data channel acts as a data transmission link between different data processing links, ensuring the smooth transmission of data from various functional modules. Based on the technical solution provided in the embodiment of the present application, in the process of processing interactive events, point-to-point data communication within the application is reduced, and there is no need to frequently transmit data between a large number of functional modules. Therefore, the interactive process of the application can be greatly simplified, the interactive efficiency and data processing efficiency of the application can be improved, and the response effect of the interactive interface and the response speed of the interactive interface are also enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0047] Figure 1 The exemplary system architecture block diagram applying the technical solution of the present application is schematically shown.

[0048] Figure 2 A schematic diagram of an application scenario in which a page interaction method is executed by a terminal device according to an embodiment of the present application is shown.

[0049] Figure 3 A flow chart of a page interaction method in one embodiment of the present application is shown.

[0050] Figure 4 A flowchart of updating page content based on a page jump event in one embodiment of the present application is shown.

[0051] Figure 5 A schematic diagram of the framework structure of forward transmission of cross-page shared data in an application scenario according to an embodiment of the present application is shown.

[0052] Figure 6 A flowchart of updating page content based on a page return event in one embodiment of the present application is shown.

[0053] Figure 7 A schematic diagram of the framework structure of reversely transmitting cross-page shared data in an application scenario in an embodiment of the present application is shown.

[0054] Figure 8 The structural block diagram of the page interaction device provided in an embodiment of the present application is schematically shown.

[0055] Fig. 9 The structure block diagram of a computer system suitable for implementing an electronic device of an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0056] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0057] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the present application.

[0058] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0059] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0060] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0061] Figure 1 An exemplary system architecture block diagram applying the technical solution of the present application is shown.

[0062] like Figure 1As shown, the system architecture 100 may include a terminal device 110, a network 120 and a server 130. The terminal device 110 may include various electronic devices such as smart phones, tablet computers, laptops, desktop computers, smart speakers, smart wearable devices, smart vehicle-mounted devices, and smart payment terminals. The server 130 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The network 120 may be a communication medium of various connection types that can provide a communication link between the terminal device 110 and the server 130, such as a wired communication link or a wireless communication link.

[0063] According to the implementation requirements, the system architecture in the embodiment of the present application can have any number of terminal devices, networks and servers. For example, the server 130 can be a server group composed of multiple server devices. In addition, the technical solution provided in the embodiment of the present application can be executed by the terminal device 110, or it can be implemented by the terminal device 110 and the server 130 together, and the present application does not make any special restrictions on this.

[0064] Figure 2 A schematic diagram of an application scenario in which a page interaction method is executed by a terminal device according to an embodiment of the present application is shown.

[0065] like Figure 2 As shown, in this application scenario, the terminal device is a smart phone held by the user, and various application clients can be installed on the terminal device, such as instant messaging software, audio and video playback software, online shopping software, network payment software, etc. In order to realize the various application functions of the application, multiple functional modules can be configured inside the application, and the complete interactive event processing flow can be realized through the mutual cooperation between the functional modules. Among them, each functional module can be responsible for executing one or more data processing links.

[0066] Through the interactive interface of the terminal device, the view pages of various applications can be presented to the user, and the user's interactive operations can be accepted, so as to adjust the display content and display effect of the view page according to the interactive operations.

[0067] like Figure 2 As shown, in this application scenario, the interactive interface of the terminal device can realize interactive functions through multiple functional modules such as view 201, view controller 202 and view model 203.

[0068] View 201 refers to the presentation layer of the interactive interface, which is responsible for displaying data from the view model and collecting user input. View 201 does not contain business logic, but connects the data in the view model and the elements displayed on the interactive interface through data binding. View 201 is responsible for receiving user interaction operations, such as clicking buttons, entering text, etc. These interaction operations can trigger corresponding data processing commands, which are defined in the view model and used to execute corresponding business logic. Since view 201 does not contain business logic, it can be more easily reused in different applications or contexts, and view 201 can be more easily unit tested due to its simplicity and separation from business logic.

[0069] The view controller 202 is a functional module responsible for managing the interaction process between the view 201 and the view model 203. The view controller 202 usually creates and initializes the view model when the view is loaded, and is responsible for instantiating the view model and passing it to the view. The view controller 202 is also responsible for setting the data binding between the view and the view model, for example, including binding the properties of the view model to the user interface elements of the view, and binding the interactive events of the view (such as button click events) to the data processing commands of the view model. The view controller 202 can manage the complete life cycle of the view, including the creation, display, hiding and destruction of the view.

[0070] The view model 203 acts as a bridge between the view and the model. Its main purpose is to separate the business logic and data processing from the view layer, making the view more concise and easy to manage. The view model 203 contains the business logic related to the user interface, and is responsible for handling the acquisition, processing and updating of data, as well as the response to user interaction operations. The view model 203 provides the data required by the view, which can be automatically updated to the view through the data binding mechanism. When the data in the view model 203 changes, the view will automatically update to reflect these changes. The view model 203 is also responsible for converting the data in the model into a format that the view can understand and display, which may include data formatting, unit conversion, etc. The view and model can be decoupled through the view model 203, so that the view can be developed and tested independently of the business logic, and the model can also be developed independently of the user interface.

[0071] In some optional implementations, the view model 203 may store data in a local storage database of the terminal device, or in a remote database of the server. When the data is stored on the server, the view model 203 may communicate with the server over the network to obtain the data from the server.

[0072] When the user triggers an interactive operation on the interactive interface through the view 201, the view controller 202 can process the user's interaction with the view 201 and forward these interactions to the view model 203. For example, when the user clicks a button, the view controller 202 calls the corresponding data processing command in the view model 203, completes the data processing process based on the data processing command, and then displays the data processing result to the user through the view 201.

[0073] In the technical solution provided in the embodiment of the present application, a first data channel 204 corresponding to the current view page can be created through the view model 203, and each functional module can transfer data between different data processing links through the first data channel 204. The data channel can be called a pipeline, which is a data flow architecture in which data is transmitted through a series of processing steps or stages, and each stage can process different parts of the data in parallel. The data channel allows data to flow between different processing units without waiting for the previous processing unit to complete all operations.

[0074] Take an online shopping application as an example. The application has a complex interactive interface that allows users to browse products, view details, add to cart, and make purchases.

[0075] When a user clicks on a product on the interactive interface, this click action is an interactive event, which triggers the following series of operations.

[0076] Writing of first attribute data: View 201 captures the interaction event of a user clicking on a product and generates first attribute data, which may include information such as the product ID, the timestamp of the user's click, the type of device that clicked, etc. This information is written into the first data channel 204 for transmission between different data processing links of the application.

[0077] Sending a data acquisition request: The view model 203 sends a data acquisition request to the server, requesting to obtain detailed information related to the product clicked by the user, such as product description, price, inventory status, etc.

[0078] Receiving the second attribute data and updating the page content: After processing the request, the server sends the detailed information of the product as the second attribute data back to the view model 203. When these data reach the view 201 through the first data channel 204, the view 201 will update the page content displayed on the interactive interface according to these second attribute data. For example, the product details page will display high-definition pictures, detailed descriptions, user reviews and other information of the product.

[0079] The page interaction method, page interaction device, computer-readable medium, electronic device, and computer program product provided by the present application are described in detail below in conjunction with specific implementation methods.

[0080] Figure 3 A flow chart of a page interaction method in an embodiment of the present application is shown. The page interaction method can be performed by Figure 1 The terminal device shown in the figure may execute the page interaction method executed by the terminal device, or the terminal device and the server may execute the page interaction method executed by the terminal device as an example. Figure 3 As shown, the page interaction method may include the following steps S310 to S330.

[0081] S310: According to an interaction event triggered on the interaction interface, first attribute data is written into a first data channel. The interaction event includes multiple data processing links. The first data channel is used to transfer data between different data processing links. The first attribute data is used to represent the attribute change information generated by the interaction interface during the initiation link of the interaction event.

[0082] The interactive interface refers to the interface for information exchange between the user and the terminal device, which may include a graphical user interface (GUI), a command line interface (CLI), or a conversational user interface (CUI), etc. Interaction events include operations performed by the user on the interactive interface, such as clicking, sliding, entering text, etc.

[0083] When a user uses application software on a terminal device, the terminal device will present a view page of the application software to the user through an interactive interface, and can also receive interactive operations performed by the user on the view page of the application software through the interactive interface.

[0084] For example, on the view page of the application software, there are usually functional controls for implementing different operating functions, such as virtual buttons, input boxes or sliding wheels, etc. In addition, the view page also has interface elements for carrying different media contents, such as video, audio, picture or text, etc.

[0085] Users can interact with the functional controls or interface elements distributed on the view page by performing interactive operations such as clicking and sliding on the interactive interface, and initiate corresponding interactive events. The triggering of interactive events will cause corresponding attribute changes in the interactive interface, which may include changes in the content displayed on the interactive interface or changes in the display effect of the view. For example, a view page displayed on the interactive interface jumps to another view page, displays the animation effect of page jump, the animation effect of closing the current page and the animation effect of loading a new page, adjusts the size of the current page, and so on.

[0086] In the initiation phase of the interactive event, the attribute change information of the interactive interface can be collected to obtain the first attribute data, and the first attribute data can be further written into the first data channel, so that the first attribute data can be passed to the next data processing phase.

[0087] In one embodiment of the present application, two adjacent data processing links may be executed on the same functional module or may be executed on different functional modules.

[0088] For example, an interactive event may include an initiation phase, a response phase, and a display phase. Figure 2 Taking the multiple functional modules shown as examples, the initiation phase of the interaction event may include receiving the interaction operation triggered by the user through the view 201; the response phase may include converting the interaction operation received by the view 201 into an executable operation command through the view controller 202, and executing the operation command through the view model 203 to obtain response data for responding to the interaction operation from the data source; the display phase may include converting the response data obtained by the view model 203 into displayable content data through the view controller 202, and displaying the view page containing the above content data on the interaction interface through the view 201.

[0089] S320: Send a data acquisition request to the data source, where the data acquisition request is used to request data that responds to the first attribute data.

[0090] A data source refers to a system, device or service unit that stores data, such as a database, file system, API interface, etc. The data source defines the location information of the data, user authentication information, and the configuration required to interact with the data. The data source in the embodiment of the present application may include a database configured locally on the terminal device, and may also include a database configured on a remote server.

[0091] Taking the application scenario of page jump as an example, when the user triggers the page jump operation on the interactive interface, a jump will be initiated from the currently displayed first page to the display of the second page, and the second page has different content data from the first page. In order to respond to the page jump operation, a data acquisition request for the content data of the second page can be initiated to the data source. Among them, the data source may include one or more. For example, the application may first search whether there is cache data of the second page in the cache of the terminal device; if the search in the cache fails, it may continue to search whether there is client local configuration data of the second page in the local hard disk of the terminal device; if the search in the local hard disk fails, it may continue to communicate data with the remote server to obtain the content data of the second page stored on the remote server.

[0092] In one embodiment of the present application, the data source includes a first data source that does not provide a connection pool and a second data source that provides a connection pool. The first data source may include, for example, the DriverManagerDataSource in Spring, and the first data source creates a new database connection for each connection request and destroys the connection after use. The second data source may include, for example, Apache Commons DBCP, C3P0, HikariCP, etc., and the second data source pre-creates a certain number of database connections and stores these connections in a pool for application reuse. Connection pool technology can significantly improve performance and reduce the overhead of connection creation and destruction.

[0093] In the Spring framework, data source configuration can be implemented through XML files or Java configuration classes. For example, when using the C3P0 connection pool, you can specify the data source type as POOLED in Spring's XML configuration file and point to the C3P0 configuration file, which defines various parameters of the connection pool, such as the maximum number of connections, the minimum number of connections, and the idle time. SpringBoot further simplifies the configuration of data sources, and it provides the function of automatically configuring data sources. In the absence of explicit configuration of data sources, Spring Boot automatically chooses to use HikariCP, Tomcat connection pool, or Commons DBCP2 based on the library under the class path. If you need to use a specific data source, you can specify it in the application.properties file. For example, when using C3P0, you can set spring.datasource.type=com.mchange.v2.c3p0.ComboPooledDataSource. The configuration of the data source includes not only connection information, but also configuration information involving security, performance optimization, and high availability. For example, it can include connection timeout, query cache, transaction isolation level, etc.

[0094] The embodiment of the present application uses the first data source and the second data source to cooperate to achieve configuration complementarity in different application scenarios. The first data source that does not provide a connection pool is suitable for scenarios with less database interaction, which can simplify application configuration and reduce resource usage; while the introduction of the second data source that provides a connection pool significantly improves the performance of high-frequency database interaction, reduces the overhead of connection creation and destruction by reusing persistent connections, optimizes resource utilization, and enhances the response speed and stability of the application in a high-concurrency environment.

[0095] S330: When second attribute data corresponding to the data acquisition request appears in the first data channel, the page content displayed on the interactive interface is updated according to the second attribute data, and the second attribute data is used to represent the attribute change information generated by the interactive interface in the response phase of the interactive event.

[0096] After the application client sends a data acquisition request to the data source, the data source can return the second attribute data as response data to the application client, and the second attribute data is used to indicate the attribute change information generated by the interactive interface in the response phase of the interactive event. The second attribute data returned by the data source will be written into the first data channel, so that the view controller and the view can monitor the second attribute data, and then update the page content displayed on the interactive interface according to the second attribute data.

[0097] In one embodiment of the present application, the interaction event includes a page jump event from a first page to a second page, and the corresponding second attribute data may include the page content to be displayed after the jump, that is, the page content of the second page. The page jump event in the embodiment of the present application may include closing the first page and opening the second page on the interactive interface, and may also include displaying the second page in other ways such as a floating window or a pop-up full-screen window above the first page.

[0098] Figure 4 A flow chart showing an embodiment of the present application in which the page content is updated based on a page jump event is shown. Figure 4 As shown, based on the above embodiment, updating the page content displayed on the interactive interface according to the second attribute data in step S330 may further include the following steps S331 to S333.

[0099] S331: Parse the second attribute data to obtain a navigation link of the second page.

[0100] By parsing the second attribute data, the navigation link of the second page carried therein can be obtained. The navigation link of the second page refers to the address of the second page in the background storage space. For example, when the data source returns response data to the application client, the page configuration data used to display the second page can be loaded into the memory. At this time, the navigation link of the second page is the memory address corresponding to the storage of the page configuration data.

[0101] In some optional implementations, the navigation link of the second page may also be a uniform resource identifier URI or a uniform resource locator URL pointing to a page resource, which is used to request to obtain the corresponding page resource.

[0102] S332: Obtain page configuration data of the second page according to the navigation link, where the page configuration data is used to represent page display content and page display effect of the second page.

[0103] The HTML, CSS, JavaScript files of the second page, as well as possible page configuration data, can be obtained according to the navigation link. Page configuration data refers to the data structure used to define the page layout, style, content, and behavior, and is used to represent the page display content and page display effect of the second page. It is usually stored in JSON, XML, or other formats and can be dynamically loaded through server-side rendering or client-side scripts.

[0104] S333: Displaying the second page on the interactive interface according to the page configuration data.

[0105] The application client parses the HTML, CSS, and JavaScript of the second page, renders the page layout and style according to the page configuration data, and thus displays the page content of the second page on the interactive interface.

[0106] The embodiment of the present application ensures accurate control of the second page content and display effect by efficiently parsing the second attribute data to obtain the navigation link, thereby achieving dynamic and flexible page rendering. The embodiment of the present application quickly loads and displays content through pre-defined page configuration data, and also improves the response speed and interaction efficiency of the application, so that the user interface can be dynamically adjusted according to the preset configuration, supports a high degree of maintainability and scalability, and provides convenience for subsequent content updates and function expansions.

[0107] In one embodiment of the present application, the method for obtaining page configuration data of a second page according to a navigation link may further include: obtaining initial page data of the second page according to the navigation link, the initial page data including data for initializing configuration of the second page; collecting first page shared data, the first page shared data including data shared from the first page to the second page; writing the first page shared data into a second data channel, the second data channel being used to transfer data between different pages; when a fusion instruction corresponding to the first page shared data appears in the second data channel, the initial page data is fused with the first page shared data according to the fusion instruction to obtain page configuration data of the second page.

[0108] The page configuration data of the second page in the embodiment of the present application includes the initial page data of the second page and the page shared data of the first page. The initial page data of the second page is the page data that can be loaded and rendered independently without relying on other pages, and the page shared data of the first page refers to the data that needs to be displayed on the second page depending on the page configuration of the first page.

[0109] For example, if the user does not perform any input operations related to the second page on the first page, when the user triggers the jump to the second page, the page configuration can be completed directly according to the initial page data of the second page, and then the second page can be displayed with the initialized content and effect.

[0110] On the contrary, if the user performs an input operation related to the second page on the first page, such as completing an account login by entering user identity information. At this time, if the user triggers a jump to the second page, it is necessary to collect the shared data of the first page and pass the shared data of the first page to the second page, so as to complete the page configuration according to the initial page data of the second page and the shared data of the first page, and display the second page in accordance with the content and effect of the user input operation. For example, private data that can only be viewed after completing the account login can be displayed to the user.

[0111] The fusion instruction may include an identifier for triggering page fusion. For example, the first page may write the first page shared data to the second data channel in the form of a data stream, and an identifier representing the fusion instruction may be written at the end of the data stream. When the second page completes receiving the second page shared data and recognizes the identifier, it may be determined that the first page has completed data transfer, and then page fusion may be triggered.

[0112] In some optional embodiments, the fusion instruction may also include a notification message for triggering page fusion. For example, the first page may write the first page shared data to the second data channel in the form of a data stream. After the complete first page shared data is completely written, a notification message representing the fusion instruction may be written to the second data channel. The notification message may include summary information of the first page shared data, such as the starting position and capacity of the first page shared data. When the second page completes receiving the second page shared data and receives the notification message, it can be determined whether the first page has completed data transfer based on the notification message, and page fusion can be triggered after confirming that the complete first page shared data has been received.

[0113] Figure 5 A schematic diagram of the framework structure of forward transmission of cross-page shared data in an application scenario according to an embodiment of the present application is shown.

[0114] like Figure 5As shown, a second data channel 503 for transferring data across pages is configured between the first page 501 and the second page 502. When the first page 501 needs to transfer the first page shared data to the second page 502, the first page shared data can be written into the second data channel 503, and after completing the writing operation of the first page shared data, a fusion instruction is written into the second data channel 503. The second page 502 can receive the first page shared data through the second data channel 503, and after receiving the fusion instruction, fuse the first page shared data with its own initial page data to obtain updated page configuration data, so as to display the second page on the interactive interface according to the updated page configuration data.

[0115] The embodiment of the present application realizes efficient and dynamic data sharing and fusion between pages by intelligently acquiring and processing cross-page data. The embodiment of the present application first extracts the initial configuration data of the second page from the navigation link, then collects the necessary shared data from the first page, and safely transmits these data across pages through the second data channel. After receiving the corresponding fusion instruction, the initial data can be cleverly combined with the shared data to generate a complete page configuration, thereby ensuring that the second page can dynamically render content and interface layout according to the latest data, improving the overall interactivity and data consistency of the application. In addition, this data fusion strategy also supports the modular design of the application, making page updates and function expansions more flexible and efficient.

[0116] In one embodiment of the present application, the interaction event also includes a page return event in which the second page returns to the first page.

[0117] Figure 6 A flow chart showing an embodiment of the present application in which the page content is updated based on a page return event is shown. Figure 6 As shown, based on the above embodiment, updating the page content displayed on the interactive interface according to the second attribute data in step S330 may further include the following steps S334 to S337.

[0118] S334: Collect second page shared data, where the second page shared data includes page data shared from the second page to the first page.

[0119] S335: Write the second page shared data into the second data channel.

[0120] S336: When a fusion instruction corresponding to the second page shared data appears in the second data channel, the second page shared data is fused with the initial page data of the first page according to the fusion instruction to obtain page update data of the first page.

[0121] S337: Displaying the first page on the interactive interface according to the page update data of the first page.

[0122] Figure 7 A schematic diagram of the framework structure of reversely transmitting cross-page shared data in an application scenario in an embodiment of the present application is shown.

[0123] like Figure 7 As shown, a second data channel 503 for transferring data across pages is configured between the first page 501 and the second page 502. When the second page 502 needs to transfer the second page shared data to the first page 501, the second page shared data can be written into the second data channel 503, and after completing the writing operation of the second page shared data, a fusion instruction is written into the second data channel 503. The first page 501 can receive the second page shared data through the second data channel 503, and after receiving the fusion instruction, the second page shared data is fused with its own initial page data to obtain the page update data of the first page, so as to display the first page on the interactive interface according to the updated data.

[0124] The implementation method and implementation effect of each method step in the embodiment of the present application can refer to the solution of forward transmission of cross-page shared data in the above embodiment, which will not be repeated here.

[0125] In one embodiment of the present application, the method for displaying a second page on an interactive interface according to page configuration data may further include: creating a second view controller, the second view controller being used to manage the display process of the second page; pushing the second view controller to the top of a navigation stack, the navigation stack being used to manage the page hierarchy displayed on the interactive interface; and displaying the second page on the interactive interface according to the second view controller and the page configuration data.

[0126] In one embodiment of the present application, the interaction event also includes a page return event in which the second page returns to the first page; after displaying the second page on the interaction interface according to the second view controller and the page configuration data, the method for displaying the second page on the interaction interface according to the page configuration data may further include: removing the second view controller from the top of the navigation stack to obtain the first view controller located below the second view controller, the first view controller being used to manage the display process of the first page; and displaying the first page on the interaction interface according to the first view controller and the page update data of the first page.

[0127] The navigation stack is used to manage the user's navigation process between different view pages. In mobile applications or web applications, the navigation stack can be used to record the page path that the user has taken from the launch of the application to the current location, as well as the view controller of each page.

[0128] The navigation stack maintains a hierarchical list of pages, each of which is an instance of a view controller. When the user enters a new page, the corresponding view controller is pushed to the top of the stack; when the user returns to the previous page, the view controller of the current page is popped from the stack. The navigation stack follows the last-in-first-out (LIFO) principle, that is, the view controller pushed last to the stack is the first to be popped, which matches the order in which the user navigates in the app. The user can trigger a navigation back operation through the back button or other interface elements, causing the current view controller to be popped from the stack and the previous view controller in the stack to be displayed.

[0129] The embodiment of the present application optimizes page management by creating a special second view controller, ensuring the efficiency and orderliness of the second page display process. By pushing the view controller into the navigation stack, the embodiment of the present application cleverly utilizes the last-in-first-out feature of the stack to maintain the page hierarchy, making page navigation both intuitive and easy to manage. In addition, combined with the page configuration data, the embodiment of the present application can ensure that the display of the second page is consistent with user expectations and application design, thereby improving the consistency of the user experience and the responsiveness of the interactive interface. The embodiment of the present application not only enhances the navigation logic of the application, but also provides strong support for dynamic content display and interface updates, improving the fluency of interface interaction and consistency of operation.

[0130] In one embodiment of the present application, before writing the first attribute data to the first data channel, an observer may be registered for the first data channel, thereby monitoring attribute changes on the first data channel based on the observer pattern. Specifically, the embodiment of the present application may call and execute an observer registration function for the first data channel, the observer registration function is used to register the attribute object held by the first data channel as an observer, and the observer is used to send a notification to the observer when the attribute changes; when the attribute of the observer changes, the observer callback function is called and executed, and the observer callback function is used to trigger a notification to the observer and obtain the attribute change information of the observer according to the notification.

[0131] The embodiment of the present application realizes efficient management and response to data state changes by designing the observer pattern. First, by calling the observer registration function, the attribute object held by the first data channel is registered as the observed object, ensuring that once the attributes of the object change, all registered observers can receive timely notifications. This mechanism not only improves the transparency and real-time performance of data processing, but also enhances the responsiveness of the system. When the attributes of the observed object change, the observer callback function is triggered, which is responsible for sending notifications to the observer and obtaining the latest attribute change information, thereby allowing the observer to update its own status or perform related operations based on this information. The embodiment of the present application simplifies the communication process between components, reduces the degree of coupling, makes the system more modular and easy to maintain, and also improves the flexibility of the application and user experience.

[0132] In one embodiment of the present application, the observer registration function includes multiple fields such as key value path, observation options and context parameters. Among them, the key value path is used to indicate the property object registered as the observer; the observation option is used to indicate the content of the notification sent by the observer when the property changes; the context parameter is used to pass an identifier to the observer callback function, and the identifier is used to distinguish different property parameters of the observer.

[0133] For example, the observer registration function in the embodiment of the present application can be expressed as addObserver:forKeyPath:options:context.

[0134] forKeyPath stands for key path. This parameter is a string that represents the key path of the property to be observed. A key path is a dot-separated path that specifies the properties in an object. For example, if the first data channel holds a property object person, the property object has an attribute parameter address, and address further includes an attribute parameter city, then the key path address.city can be used to specify the property to be observed.

[0135] Options stands for observation options, which specifies some options when observing attributes. It is a bit mask that can include a combination of one or more field values ​​as follows.

[0136] NSKeyValueObservingOptionNew: Provides the new value of a property in a callback.

[0137] NSKeyValueObservingOptionOld: Provides the old value of a property in the callback.

[0138] NSKeyValueObservingOptionInitial: Sends a notification once, immediately when observation begins, regardless of whether the value changes.

[0139] NSKeyValueObservingOptionPrior: Send a notification before the property value actually changes.

[0140] context stands for context parameter, which is a pointer to any type. The context parameter will be passed back to the observer callback method, allowing you to distinguish which attribute has changed when observing multiple attributes using the same callback method. You can usually use the context parameter to pass an identifier or custom data.

[0141] The observer callback function in the embodiment of the present application can be expressed as observeValueForKeyPath:ofObject:change:context, for example. The context parameter is used to identify which attribute observer is triggered, so that even if multiple attributes are observed using the same callback method, it is possible to identify which attribute has changed.

[0142] In one embodiment of the present application, after the page content displayed on the interactive interface is updated according to the second attribute data, an observer removal function of the first data channel is called to cancel the observed person registration operation for the first data channel.

[0143] For example, the observer removal function in the embodiment of the present application can be expressed as removeObserver:forKeyPath. Among them, observer is a pointer to the observer, that is, the same object used when adding the observer before. This object needs to implement the NSKeyValueObserving protocol and override the observeValueForKeyPath:ofObject:change:context: method to receive the observed changes. keyPath is a key value path string that specifies the property to stop observing, and the key value path is exactly the same as the key value path used when adding the observer before.

[0144] In the embodiment of the present application, when there is no need to observe changes in a certain property, or when the observer (such as a view controller) is about to be destroyed, the observer removal function can be called to remove the observer to avoid potential memory leaks and unnecessary observer callbacks.

[0145] Based on the introduction of the above embodiments and application scenarios, it can be seen that the present application utilizes a first data channel configured vertically and a second data channel configured horizontally to achieve efficient data transmission between different data processing links and different view pages. In the process of processing interactive events, point-to-point data communication within the application is reduced, and there is no need to frequently transfer data between a large number of functional modules. Therefore, it can greatly simplify the interactive process of the application, improve the interactive efficiency and data processing efficiency of the application, and also enhance the response effect of the interactive interface and improve the response speed of the interactive interface.

[0146] It should be noted that although the steps of the method in the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0147] The following introduces an apparatus embodiment of the present application, which can be used to execute the page interaction method in the above-mentioned embodiment of the present application. Figure 8 The structure block diagram of the page interaction device provided in the embodiment of the present application is schematically shown. Figure 8 As shown, the page interaction device 800 includes:

[0148] The writing module 810 is configured to write the first attribute data into the first data channel according to the interaction event triggered on the interaction interface, the interaction event includes multiple data processing links, the first data channel is used to transfer data between different data processing links, and the first attribute data is used to represent the attribute change information generated by the interaction interface in the initiation link of the interaction event;

[0149] A sending module 820 is configured to send a data acquisition request to a data source, wherein the data acquisition request is used to request to acquire data that responds to the first attribute data;

[0150] The update module 830 is configured to update the page content displayed on the interactive interface according to the second attribute data when the second attribute data corresponding to the data acquisition request appears in the first data channel, and the second attribute data is used to represent the attribute change information generated by the interactive interface in the response phase of the interactive event.

[0151] In some embodiments of the present application, based on the above technical solution, the interaction event includes a page jump event from a first page to a second page; the update module 830 includes:

[0152] A parsing module, configured to parse the second attribute data to obtain a navigation link of the second page;

[0153] The acquisition module is configured to acquire page configuration data of the second page according to the navigation link, wherein the page configuration data is used to represent page display content and page display effect of the second page;

[0154] The first display module is configured to display the second page on the interactive interface according to the page configuration data.

[0155] In some embodiments of the present application, based on the above technical solution, the acquisition module further includes:

[0156] an initial acquisition module, configured to acquire initial page data of the second page according to the navigation link, wherein the initial page data includes data for initializing configuration of the second page;

[0157] A first acquisition module is configured to acquire first page shared data, where the first page shared data includes data shared from the first page to the second page;

[0158] A first writing module is configured to write the first page shared data into a second data channel, where the second data channel is used to transfer data between different pages;

[0159] The first fusion module is configured to fuse the initial page data with the first page shared data according to the fusion instruction to obtain page configuration data of the second page when a fusion instruction corresponding to the first page shared data appears in the second data channel.

[0160] In some embodiments of the present application, based on the above technical solution, the interaction event further includes a page return event in which the second page returns to the first page; and the update module 830 further includes:

[0161] A second collection module is configured to collect second page shared data, where the second page shared data includes page data shared by the second page to the first page;

[0162] A second writing module is configured to write the second page shared data into the second data channel;

[0163] a second fusion module, configured to, when a fusion instruction corresponding to the second page shared data appears in the second data channel, fuse the second page shared data with the initial page data of the first page according to the fusion instruction to obtain page update data of the first page;

[0164] The second display module is configured to display the first page on the interactive interface according to the page update data of the first page.

[0165] In some embodiments of the present application, based on the above technical solution, the first display module further includes:

[0166] A view creation module is configured to create a second view controller, where the second view controller is used to manage the display process of the second page;

[0167] A view push module, configured to push the second view controller to the top of a navigation stack, where the navigation stack is used to manage a page hierarchy displayed on the interactive interface;

[0168] The view display module is configured to display the second page on the interactive interface according to the second view controller and the page configuration data.

[0169] In some embodiments of the present application, based on the above technical solution, the interaction event also includes a page return event in which the second page returns to the first page; and the second display module further includes:

[0170] A view removal module is configured to remove the second view controller from the top of the navigation stack to obtain a first view controller located below the second view controller, wherein the first view controller is used to manage the display process of the first page;

[0171] The view update module is configured to display the first page on the interactive interface according to the page update data of the first view controller and the first page.

[0172] In some embodiments of the present application, based on the above technical solution, the page interaction device 800 further includes:

[0173] A first function calling module is configured to call and execute an observer registration function of the first data channel, wherein the observer registration function is used to register the attribute object held by the first data channel as an observer, and the observer is used to send a notification to the observer when the attribute changes;

[0174] The second function calling module is configured to call and execute the observer callback function when the attribute of the observed object changes, and the observer callback function is used to trigger a notification to the observer and obtain the attribute change information of the observed object according to the notification.

[0175] In some embodiments of the present application, based on the above technical solution, the observer registration function includes the following fields:

[0176] The key value path is used to indicate the property object registered as the observer;

[0177] Observation options, used to indicate the content of the notification sent by the observed object when the attribute changes;

[0178] The context parameter is used to pass an identifier to the observer callback function, where the identifier is used to distinguish different attribute parameters of the observed object.

[0179] In some embodiments of the present application, based on the above technical solution, the page interaction device 800 further includes:

[0180] The third function calling module is configured to call and execute an observer removal function of the first data channel, where the observer removal function is used to cancel an observer registration operation for the first data channel.

[0181] The specific details of the page interaction device provided in each embodiment of the present application have been described in detail in the corresponding method embodiment and will not be repeated here.

[0182] Fig. 9 The structure block diagram of a computer system for implementing an electronic device according to an embodiment of the present application is schematically shown.

[0183] It should be noted that Fig. 9 The computer system 900 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0184] like Fig. 9 As shown, the computer system 900 includes a central processing unit 901 (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 902 (ROM) or the program loaded from the storage part 908 to the random access memory 903 (RAM). Various programs and data required for system operation are also stored in the random access memory 903. The central processing unit 901, the read-only memory 902 and the random access memory 903 are connected to each other through a bus 904. An input / output interface 905 (Input / Output interface, i.e., I / O interface) is also connected to the bus 904.

[0185] The following components are connected to the input / output interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed so that a computer program read therefrom is installed into the storage section 908 as needed.

[0186] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the central processor 901, various functions defined in the system of the present application are executed.

[0187] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0188] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0189] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0190] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0191] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not disclosed in the present application.

[0192] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A page interaction method, characterized in that: include: Writing first attribute data into a first data channel according to an interaction event triggered on the interaction interface, wherein the interaction event includes a plurality of data processing links, the first data channel is used to transfer data between different data processing links, and the first attribute data is used to represent attribute change information generated by the interaction interface in the initiation link of the interaction event; Sending a data acquisition request to a data source, wherein the data acquisition request is used to request to acquire data that responds to the first attribute data; When second attribute data corresponding to the data acquisition request appears in the first data channel, the page content displayed on the interactive interface is updated according to the second attribute data, and the second attribute data is used to represent the attribute change information generated by the interactive interface in the response phase of the interactive event.

2. The page interaction method according to claim 1, characterized in that: The interaction event includes a page jump event of jumping from a first page to a second page; Updating the page content displayed on the interactive interface according to the second attribute data includes: Parsing the second attribute data to obtain a navigation link of the second page; Acquire page configuration data of the second page according to the navigation link, wherein the page configuration data is used to represent page display content and page display effect of the second page; The second page is displayed on the interactive interface according to the page configuration data.

3. The page interaction method according to claim 2, characterized in that: Acquiring page configuration data of the second page according to the navigation link includes: Acquire initial page data of the second page according to the navigation link, wherein the initial page data includes data for initializing configuration of the second page; Collecting first page shared data, where the first page shared data includes data shared from the first page to the second page; Writing the first page shared data into a second data channel, where the second data channel is used to transfer data between different pages; When a fusion instruction corresponding to the first page shared data appears in the second data channel, the initial page data is fused with the first page shared data according to the fusion instruction to obtain page configuration data of the second page.

4. The page interaction method according to claim 2, characterized in that: The interaction event includes a page return event of returning from the second page to the first page; Updating the page content displayed on the interactive interface according to the second attribute data includes: Collecting second page shared data, where the second page shared data includes page data shared by the second page to the first page; Writing the second page shared data into the second data channel; When a fusion instruction corresponding to the second page shared data appears in the second data channel, the second page shared data is fused with the initial page data of the first page according to the fusion instruction to obtain page update data of the first page; The first page is displayed on the interactive interface according to the page update data of the first page.

5. The page interaction method according to claim 2, characterized in that: Displaying the second page on the interactive interface according to the page configuration data includes: Creating a second view controller, where the second view controller is used to manage the display process of the second page; Pushing the second view controller to the top of a navigation stack, the navigation stack being used to manage a hierarchy of pages displayed on the interactive interface; The second page is displayed on the interactive interface according to the second view controller and the page configuration data.

6. The page interaction method according to claim 5, characterized in that: The interaction event also includes a page return event in which the second page returns to the first page; After displaying the second page on the interactive interface according to the second view controller and the page configuration data, the method further includes: Remove the second view controller from the top of the navigation stack to obtain a first view controller located below the second view controller, where the first view controller is used to manage the display process of the first page; The first page is displayed on the interactive interface according to the first view controller and the page update data of the first page.

7. The page interaction method according to any one of claims 1 to 6, characterized in that: Before writing the first attribute data into the first data channel, the method further includes: Calling and executing an observer registration function of the first data channel, wherein the observer registration function is used to register the attribute object held by the first data channel as an observer, and the observer is used to send a notification to the observer when the attribute changes; When the observed object has a property change, the observer callback function is called and executed, and the observer callback function is used to trigger a notification to the observer and obtain the property change information of the observed object according to the notification.

8. The page interaction method according to claim 7, characterized in that: The observer registration function includes the following fields: The key value path is used to indicate the property object registered as the observer; Observation options, used to indicate the content of the notification sent by the observed object when the attribute changes; The context parameter is used to pass an identifier to the observer callback function, where the identifier is used to distinguish different attribute parameters of the observed object.

9. The page interaction method according to claim 7, characterized in that: After updating the page content displayed on the interactive interface according to the second attribute data, the method further includes: An observer removal function of the first data channel is called and executed, where the observer removal function is used to cancel an observer registration operation for the first data channel.

10. A page interaction device, characterized in that: include: a writing module, configured to write first attribute data into a first data channel according to an interaction event triggered on the interaction interface, wherein the interaction event includes a plurality of data processing links, the first data channel is used to transfer data between different data processing links, and the first attribute data is used to represent attribute change information generated by the interaction interface during the initiation link of the interaction event; a sending module, configured to send a data acquisition request to a data source, wherein the data acquisition request is used to request to acquire data that responds to the first attribute data; The update module is configured to update the page content displayed on the interactive interface according to the second attribute data when the second attribute data corresponding to the data acquisition request appears in the first data channel, and the second attribute data is used to represent the attribute change information generated by the interactive interface in the response phase of the interactive event.

11. A computer readable medium, characterized in that The computer-readable medium stores a computer program, and when the computer program is executed by a processor, the page interaction method according to any one of claims 1 to 9 is implemented.

12. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; Wherein, the processor is configured to execute the executable instructions to implement the page interaction method as described in any one of claims 1 to 9.

13. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the page interaction method described in any one of claims 1 to 9 is implemented.

Images