Data linkage method and device of page module, equipment and medium

Abstract

The invention relates to the technical field of development, can be applied to the technical field of health care and old-age care, and discloses a data linkage method, device and equipment of a page module and a medium. The method comprises the steps that at least one preset instantiation object is created in a memory, and the preset instantiation object is configured with a subscription method so as to be called by the linked and bound page module; when any page module bound in a linkage mode calls the subscription method, event change information triggered by the subscription method is transmitted to the page module bound in the linkage mode; and after the linkage bound page module receives the event change information, executing corresponding data change according to the event change information. A subscription mode is provided for the page module through the instantiation object, when the data structure of the publisher changes, the bound page module is linked to execute corresponding data changes, and the consistency of the page modules in the data linkage process is ensured.

Description

Technical Field

[0001] The present invention relates to the field of development technology and can be applied to the field of health care and elderly care technology, and in particular to a data linkage method, device, equipment and medium for a page module. Background Art

[0002] As people's living standards improve, the elderly's demand for elderly care services is becoming more and more diversified. The front-end framework can be used to build complex front-end pages to achieve dynamic display and interaction of data.

[0003] In related technologies, the front-end framework can develop components of different functional modules for health care and elderly care, such as health data display components, service appointment components, etc. As page modules, data linkage of page modules can be achieved by monitoring data change events of page modules through chart tools. In order to ensure that the data is presented in the most appropriate way, different data features need to match corresponding visualization styles. Chart tools usually bind data to specific styles based on internal logic and rendering mechanisms. However, this linkage binding has a strict dependence on the page structure and cannot be flexibly changed. The corresponding data can only be modified by accessing the page modules one by one, making it difficult to maintain the consistency of the page modules during the data linkage process. Summary of the Invention

[0004] The present invention provides a data linkage method, device, computer equipment and medium for page modules to solve the technical problem that related technologies cannot flexibly change the linkage binding between data and specific styles, and it is difficult to maintain the consistency of page modules during the data linkage process.

[0005] In a first aspect, a data linkage method for a page module is provided, comprising:

[0006] Creating at least one preset instantiation object in memory, wherein the preset instantiation object is configured with a subscription method for being called by the linked binding page module;

[0007] When any page module bound by linkage calls the subscription method, the event change information triggered by the subscription method is passed to the page module bound by linkage;

[0008] After the linked and bound page module receives the event change information, it performs corresponding data changes according to the event change information.

[0009] In a second aspect, a data linkage device for a page module is provided, comprising:

[0010] A creation module, configured to create at least one preset instantiation object in memory, wherein the preset instantiation object is configured with a subscription method for being called by the linked binding page module;

[0011] A transmission module, configured to transmit the event change information triggered by the subscription method to the linked and bound page module when any linked and bound page module calls the subscription method;

[0012] The linkage module is used to execute corresponding data changes according to the event change information after the linkage-bound page module receives the event change information.

[0013] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the data linkage method of the above-mentioned page module when executing the computer program.

[0014] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the data linkage method of the above-mentioned page module are implemented.

[0015] In the scheme implemented by the data linkage method, device, computer equipment and storage medium of the above-mentioned page module, at least one preset instantiation object can be created in the memory by the server, and the preset instantiation object is configured with a subscription method for the linkage-bound page module to call; when any linkage-bound page module calls the subscription method, the event change information triggered by the subscription method is passed to the linkage-bound page module in the client; after the linkage-bound page module in the client receives the event change information, it executes the corresponding data change according to the event change information. In the present invention, a subscription mode is provided for the page module by instantiating the object. When the publisher's data structure changes, the linkage-bound page module executes the corresponding data change, which can ensure the consistency of each page module in the data linkage process. This process only requires the publisher to meet the data structure requirements, and there is no need to modify the existing page structure. Personalized page modules can be customized, so that the page modules can be flexibly bound. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0017] Figure 1 This is a schematic diagram of an application environment of a data linkage method for page modules in one embodiment of the present invention;

[0018] Figure 2 This is a flow chart of a data linkage method for page modules according to an embodiment of the present invention;

[0019] Figure 3 This is a flow chart of a data linkage method for page modules according to another embodiment of the present invention;

[0020] Figure 4 yes Figure 3 A schematic flow chart of a specific implementation of step S40;

[0021] Figure 5 yes Figure 1 A schematic flow chart of a specific implementation of step S20;

[0022] Figure 6 yes Figure 1 A schematic flow chart of a specific implementation of step S60;

[0023] Figure 7 This is a block diagram of a scenario architecture for data linkage of page modules in one embodiment of the present invention;

[0024] Figure 8 This is a structural diagram of a data linkage device for a page module in one embodiment of the present invention;

[0025] Figure 9 is a structural diagram of a computer device in one embodiment of the present invention;

[0026] Figure 10 FIG. 2 is another structural diagram of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0028] The data linkage method of the page module provided by the embodiment of the present invention can be applied to Figure 1In an application environment, the server creates at least one preset instantiation object in memory, and the preset instantiation object is configured with a subscription method for the linkage-bound page module to call; when any linkage-bound page module calls the subscription method, the event change information triggered by the subscription method is passed to the linkage-bound page module in the client; after the linkage-bound page module in the client receives the event change information, it executes the corresponding data change according to the event change information. In the present invention, a subscription mode is provided for the page module by instantiating the object. When the publisher's data structure changes, the linkage-bound page module executes the corresponding data change, which can ensure the consistency of each page module in the data linkage process. This process only requires the publisher to meet the data structure requirements, without modifying the existing page structure, and can customize the personalized page module, so that the page module can be flexibly bound. Among them, the client can be but is not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices. The server can be implemented with an independent server or a server cluster composed of multiple servers. The present invention is described in detail below through specific embodiments.

[0029] See also Figure 2 As shown, Figure 2 A flow chart of a data linkage method for page modules provided in an embodiment of the present invention includes the following steps:

[0030] S10: creating at least one preset instanced object in memory.

[0031] The data linkage method of the page modules provided by the present invention can be applied to the page development scenario of health care and elderly care. The corresponding page modules can be different functional partitions in the health care and elderly care application or system interface. Each page module has specific functions and roles for displaying and processing different types of information or operations. The linkage of specific page modules can be that when the data in the health management module shows that the health status of the elderly has changed, such as an abnormality of a certain vital sign indicator, the system automatically generates a nursing reminder in the nursing service module, prompting the nursing staff to pay attention to the elderly's condition and adjust the nursing plan in time. The linkage of page modules can also be that the nursing operations and observations recorded by the nursing staff in the nursing service module, such as the elderly's medication status, physical condition changes, etc., will be synchronized to the health management module, providing doctors and other nursing staff with more comprehensive health data for comprehensive evaluation and diagnosis. The linkage of page modules can also be that the family communication module obtains the elderly's health data in the health management module, the nursing records in the nursing service module, the service order information in the life service module, and the activity participation in the social entertainment module in real time, so that the family can fully understand the elderly's life and health status in the health care institution.

[0032] In this embodiment, a preset instantiated object is a specific entity created in memory based on the class definition. It possesses the attributes and methods defined by the class and is a specific manifestation of the class. Each preset instantiated object has its own independent memory space for storing its unique attribute values. For example, health care and elderly care services include "nursing bed" and "nursing service items." The instantiated object for "nursing bed" can be a specific bed with its specific attribute values, such as its number, room location, and status. The instantiated object for "nursing service item" can be a specific service, such as "rehabilitation and physiotherapy," with corresponding specific attributes such as service duration, price, and service personnel. These instantiated objects can execute the methods defined in their respective classes, such as check-in / check-out and reservation / cancellation of services. These instantiated objects are equivalent to the mapping of specific objects in the real world in computer memory. Operations on them are used to process actual health care and elderly care services.

[0033] Specifically, when creating at least one preset instantiated object in memory, the object's class is determined. Memory space is then allocated for the object, sufficient to store all of the object's attributes and related information. The object's attributes are then initialized, assigning default values ​​or values ​​tailored to specific needs. If the object depends on other objects or resources, these dependencies must be associated and loaded accordingly to ensure that the object is available in memory and can respond to requests and operations from other modules or objects.

[0034] For example, in a healthcare and elderly care scenario, the data linkage process within the page module can create an in-memory instance of an "ElderlyUser" object. Typically, in user management systems, the "User" class is defined to contain common properties and methods, such as basic user information and login-related information. When a specific "ElderlyUser" instance is created, the corresponding attributes in memory are populated with the individual's information according to the "User" class definition. For example, if there is an elderly person named "Mr. Li," age 75, and contact information 132xxxxxxxx, then the name attribute of this "ElderlyUser" instance created in memory will be assigned the value "Mr. Li," the age attribute will be assigned the value "75," and the contact information attribute will be assigned the value "132xxxxxxxx." The instance also contains the methods defined by the "User" class. For example, if Mr. Li needs to log in to the system to view his health report, he can call the "Login" method in the instance to complete the login process.

[0035] In actual application scenarios, the preset instantiation object is configured with a subscription method for the linked page module to call. The linked page module does not need to pay attention to the internal implementation details of the preset instantiation object, but only needs to pay attention to how to receive and process data update notifications. In order to better maintain the relationship between the linked page module and the preset instantiation object, further, such as Figure 3 As shown, before step S10, the method further includes the following steps:

[0036] S40: During the initialization process of the preset instantiation object, a subscription relationship is established between the linked and bound page module and the preset instantiation object.

[0037] In this embodiment, during initialization, the preset instantiated object creates a data structure, such as a list or dictionary, for storing subscriber information. This data structure is used to record all page modules that have established subscription relationships with the instantiated object, i.e., linked and bound page modules. A subscription method is also defined in the preset instantiated object. This subscription method can implement different functions, such as adding an incoming page module object to the data structure storing subscribers or deleting a page module object from the subscriber's data structure.

[0038] Specifically, if Figure 4 As shown, in step S40, that is, during the initialization process of the preset instantiated object, a subscription relationship is established between the linked and bound page module and the preset instantiated object, including the following steps:

[0039] S41: extracting dependent fields of the page modules in the data space according to the linked and bound page modules.

[0040] S42: Determine the data linkage logic of the page module according to the dependency fields of the page module.

[0041] S43: During the initialization process of the preset instantiation object, a subscription relationship is established between the linked and bound page module and the preset instantiation object according to the data linkage logic of the page module.

[0042] In step S41, the page contains various page modules, such as text boxes, labels, drop-down lists, radio buttons, check boxes, tables, and charts. Each page module may correspond to one or more dependent fields in the data space. For example, a text box is used to display or enter a specific field value, while a drop-down list's options are derived from an enumerated field in the data space.

[0043] As an implementation method, the dependent fields of page modules in the data space can be determined by examining the linkage effects between page modules. If changes in one page module result in content updates in another module, then a data dependency may exist between the two modules. For example, in a page with a master-detail relationship, selecting an item in the master list will display detailed information related to that item in the detail list. This linkage can be analyzed to determine the fields in the master list that the detail list depends on.

[0044] As another implementation, the dependent fields of page modules in the data space can be determined by analyzing the behavior of page modules under different operations. For example, when a "Search" button is clicked, the search results displayed on the page may depend on multiple fields. By analyzing the logic of the search function, the dependent fields of the "Search" button can be determined.

[0045] In step S42, the data linkage logic is the logic for the data in the page module to be linked and changed based on the data changes in the data space. Specifically, the role of the dependent sub-field in the page module can be determined according to the function of the page module, and the data linkage logic of the page module can be determined accordingly. For example, in the page module for data display, the dependent field is used to obtain and present data. The linkage logic can obtain the corresponding dependent field value from the data source and display it on the page according to different query conditions or screening conditions. For example, in the page module for data entry, the dependent field may involve data verification and associated updates. When the "order amount" is entered, the value of the "tax amount" field is automatically calculated according to the "tax rate" field, and the value of the "total amount" field is updated accordingly. Specifically, the data linkage logic of the page module can also be determined according to the position and role of the page module in the business process. For example, in a page module of an approval process, dependent fields include "Approval Status", "Submission Time" and "Approver", etc. The data linkage logic is determined by business rules. When the "Approval Status" changes from "Pending Approval" to "Passed", the status of related records is automatically updated, and it may trigger data updates of other page modules in subsequent processes, including updating the salable quantity of corresponding products in the inventory page module.

[0046] It can be understood that the data linkage logic can clarify the functions and data interaction methods between each page module. During the initialization process, the page module needs to identify which data requires linkage effects and register the linkage logic of the corresponding data to the preset instantiated object. For example, the inventory display module and the price calculation module need to be registered with the "commodity object". The linkage logic of the inventory display module can be that the commodity object increases by 1, and the corresponding inventory display module increases by 1. The linkage logic of the price calculation module can be that the commodity object increases by 1, and the corresponding price calculation module multiplies by the unit price a.

[0047] Specifically, according to the data linkage logic, relevant events can be defined in the preset instantiation object, and at the same time, the relevant operations of the page module can be associated with these events. Accordingly, when the event is triggered, the preset instantiation object will pass the relevant data to the subscribed page module. At the same time, the page module sets a callback function to receive data and perform corresponding update operations. For example, the preset instantiation object is a product object. When the data space of the product object changes, a "change event" is triggered. The product object triggers the "update inventory display" operation and the "recalculate price" operation, triggering a change event and passing the changed specification information and related price and inventory data to the inventory display module and the price calculation module. At the same time, after the callback function of the inventory display module receives the new inventory data, it updates the inventory display information on the page. The callback function of the price calculation module recalculates and updates the display of the total price of the product on the page based on the new specifications and price data.

[0048] Considering that the page modules may rely on multiple different types of data, which may come from different data sources, and the data formats, update frequencies, and access methods of different data sources may be different, data integration and processing are required to ensure data consistency and accuracy. In other words, the linkage binding between page modules is very complex. In order to ensure the accuracy of the linkage between page modules, multiple linkage binding relationships can be established for the page modules. Furthermore, before step S10, the method also includes the following steps:

[0049] S50: Determine at least one linkage binding relationship between the page modules based on the data flow and dependency relationship between the page modules.

[0050] In this embodiment, the data flow direction between page modules can be determined by the data starting point and the data end point. Accordingly, the direction from the data starting point to the data end point is equivalent to the data flow direction between page modules. For example, in an e-commerce website, product information is usually obtained from the product database module and then flows to the product display module, shopping cart module, etc. Then the product database module is the data starting point, and the product display module and the shopping cart module are one of the data end points. The data flow direction between page modules is also obtained by tracking the data transmission process. Accordingly, the transmission path is equivalent to the data flow direction between page modules. Taking the user login process as an example, the login information entered by the user starts from the login form module and passes through the identity authentication module. If the verification is successful, the relevant user permission data will be passed to each functional module to determine which content the user can access. Here, there is a linkage relationship based on the data flow between the login form module, the identity authentication module and the various functional modules.

[0051] In this embodiment, the dependency relationships between page modules include direct dependencies and indirect dependencies. Direct dependencies can be determined by judging whether the functional implementation of the page module relies on data or services provided by other modules. For example, the order settlement module needs to rely on the commodity unit price information provided by the commodity price module and the commodity quantity information provided by the shopping cart module to calculate the total price. This direct data dependency indicates that there is a linkage binding relationship between the order settlement module and the commodity price module and the shopping cart module. Indirect dependencies can be determined by judging whether the functional implementation of the page module is connected to other modules through an intermediate module. For example, the task progress display module relies on the task allocation module and the user status module. The task allocation module assigns tasks to users, and the user status module records the user's work status. The task progress display module needs to display the progress of the task based on the data of these two modules. Although the task progress display module and the user status module do not have direct data interaction, an indirect dependency is generated through the task allocation module, indicating that there is a potential linkage relationship between them.

[0052] It's understandable that the data flows and dependencies between page modules can reveal the potential linkages between them. By analyzing the data flows and dependencies between page modules, we can more comprehensively identify the linkages and bindings between them. In practical applications, each page module may have multiple such linkages and bindings, collectively forming a complex interaction and data flow system for the page.

[0053] Correspondingly, in S10, for a linkage binding relationship, a preset instantiation object is created in the memory.

[0054] For example, function a of page module A needs to be linked and bound with page module B and page module C. An instantiated object can be created for page module A, page module B and page module C. Function b of page module A needs to be linked and bound with page module D. An instantiated object can be created for page module A and page module D.

[0055] S20: When any linked and bound page module calls the subscription method, the event change information triggered by the subscription method is transmitted to the linked and bound page module.

[0056] In this embodiment, the preset instantiation object needs to maintain a subscriber list. When the page module calls the subscription method, the relevant information of the page module (such as callback function, identity identifier, etc.) will be added to this list, and the event change will be triggered at the same time to obtain the event change information. Here, the event change information includes but is not limited to the event type, related data and other necessary metadata. Then, after the preset instantiation object receives the event change information, it traverses the subscriber list and sends the event change information to the corresponding linkage bound to the page module according to the subscription information in the subscriber list. Here, a variety of methods can be used to transmit information, such as callback function, message queue, etc. Taking the callback function as an example, the preset instantiation object will call the callback function provided by each subscription page module and pass the event change information as a parameter to these functions. For example, the news details page module provides a callback function. When a new comment is published, the preset instantiation object will call the function and pass the relevant information of the new comment so that the news details page can be updated and display the new comment in time.

[0057] It's understandable that instantiated objects can encapsulate event-related logic and data within themselves, facilitating unified management and maintenance of event triggering conditions, propagation methods, and related data. The instantiated object is pre-set as the publisher, storing the data space. The linked page module acts as the subscriber, making changes to the data space by calling subscription methods.

[0058] Correspondingly, S20, when any linked and bound page module calls the subscription method to change the data space, the change information of the data space is transmitted to the linked and bound page module.

[0059] Specifically, when a linked page module acts as a subscriber, it establishes a close connection with the publisher. That is, the page module changes the data space by calling the subscription method. Different page modules can subscribe to corresponding data changes according to their own needs. When the data in the data space changes, the relevant page modules can receive timely notifications and make corresponding updates, thereby ensuring the consistency and real-time performance of the page display and improving the maintainability and scalability of the code. If you need to modify the data or add new functions, you only need to perform the corresponding operations in the instantiated object without affecting other unrelated page modules.

[0060] Specifically, if Figure 5 As shown, in step S20, that is, when any linked and bound page module calls the subscription method to change the data space, the change information of the data space is transmitted to the linked and bound page module, including the following steps:

[0061] S21: When any linked and bound page module calls the subscription method to change the data space, the broadcast method is called to trigger a change event, so as to obtain event change information corresponding to the data space through the change event.

[0062] S22: traverse the linked and bound page modules, and call the callback function of each page module in turn, so as to transmit the event change information to the linked and bound page modules through the callback function.

[0063] For step S21, the preset instantiated object cannot be changed by external methods, and the data space can implement various change operations through the subscription method. Here, the change operations can include but are not limited to adding, deleting, querying, and modifying. The subscription method can be called by any page module that is externally linked and bound. After the page module calls the subscription method, the data space monitors the change operation and calls the broadcast method to trigger the change event to obtain the event change information. The purpose of calling the broadcast method here is to notify all linked and bound page modules that a data change event has occurred. For example, the product information publisher in the e-commerce system calls the broadcast method after the inventory data changes, and sends a change event to all page modules that have subscribed to the product data, such as the product details page module and the shopping cart page module.

[0064] It's understandable that each page module, acting as a subscriber, registers its own callback function with the preset instantiated object after calling the subscription method. When an event causes a change in the data space, the publisher begins iterating through the list of linked and bound page modules. For each page module in the list, the publisher executes its callback function, passing the changed news data as a parameter.

[0065] S30: After the linked and bound page module receives the event change information, it performs corresponding data changes according to the event change information.

[0066] In this embodiment, upon receiving event change information, the linked page module will parse the event change information according to its own business logic and convert the parsed information into a data format that the page module can understand and operate. For example, upon receiving new comments on a news detail page, the comment list displayed on the page will be updated. For another example, upon receiving information about an article update, the recommendation system module may recalculate the article's recommendation weight.

[0067] In actual application scenarios, each page module bound to the linkage has its own specific custom parameter logic. Different parameter logics will cause the page modules to produce different linkage strategies. Specifically, Figure 6As shown, step S30, that is, after the linked and bound page module receives the event change information, executing corresponding data changes according to the event change information, includes the following steps:

[0068] S31. After the linked and bound page modules receive the event change information, they extract event change parameters from the event change information according to the parameter parsing logic customized by each page module.

[0069] S32. Execute data changes in the corresponding page module according to the event change parameters, so that the data changes in the page module are linked to the event change parameters.

[0070] In this embodiment, the page module may parse the event change information according to the custom parameter parsing logic, and extract the event change parameters that conform to the custom logic based on the parsing.

[0071] For example, the task progress page module focuses on the changes in the completion percentage of the task, and its parsing logic will extract parameters related to the completion percentage from the event change information. The parsing logic of the task allocation page module focuses more on relevant parameters such as the person in charge of the task, and its parsing logic will extract parameters related to the person in charge from the event change information.

[0072] It's understood that event change parameters are variable parameters generated in the data space after the linked page calls the subscription method, and are used to link data changes in the page module. For example, if the event change parameter is a product object with a sales volume increase of 1, the inventory quantity in the corresponding page module will be reduced by 1.

[0073] In actual applications, the scenario architecture for data linkage of specific page modules can be found in Figure 7 As shown, the page module class of linkage binding can be page module A, page module B and other page modules. The page module of linkage binding can act as a subscriber, and can call the subscription method to change the data space, and at the same time call the broadcast method to trigger the change event, obtain the event change information of the data space, and pass the event change information to the page module of linkage binding, so that the page module of linkage binding can carry out data linkage of its own page module according to the event change information. It is understandable that each page module can call the subscription method provided by the instantiated object when data linkage is required, including but not limited to insert, delete, update, select, so that the data space can be modified, and then the change event triggered by the broadcast method is passed to other page modules of linkage binding.

[0074] In practical applications, the data linkage process of the page module can be applied to page development scenarios for health care and elderly care. Considering the diverse business models within health care and elderly care, such as healthcare, meal services, remote monitoring, social activities, and nursing services, for healthcare, electronic medical records can be linked to diagnosis and treatment information. The electronic medical record page records the patient's medical history, diagnosis history, medication usage, and other information. When a doctor diagnoses a patient on the diagnosis and treatment page, the system automatically links the electronic medical record, providing comprehensive reference for a more accurate diagnosis and treatment plan. Examination results can also be linked to health assessments. The examination and testing page displays the patient's various examination and test reports, such as blood count and electrocardiogram results. Based on these results, the system automatically generates a corresponding health assessment report on the health assessment page, analyzing the patient's physical condition and providing targeted health recommendations. For meal services, nutritional requirements can be linked to recipe development. Specifically, the nutritional requirements page calculates the patient's daily nutritional needs based on information such as health status, age, and weight. The system then generates personalized recipes based on these nutritional requirements on the recipe development page, ensuring a balanced nutritional intake. You can also link food inventory with procurement management. The food inventory page displays the inventory quantity of each type of food in real time. When the inventory falls below the set safety stock, the system will automatically generate a purchase order on the procurement management page, reminding the procurement staff to purchase food in time.

[0075] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0076] In one embodiment, a data linkage device for a page module is provided, which corresponds to the data linkage method for the page module in the above embodiment. Figure 8 As shown, the data linkage device of the page module includes a creation module 101, a transmission module 102 and a linkage module 103. The detailed description of each functional module is as follows:

[0077] A creation module 101 is configured to create at least one preset instantiation object in memory, wherein the preset instantiation object is configured with a subscription method for being called by a linked binding page module;

[0078] The transmission module 102 is used to transmit the event change information triggered by the subscription method to the linked and bound page module when any linked and bound page module calls the subscription method;

[0079] The linkage module 103 is configured to execute corresponding data changes according to the event change information after the linkage-bound page module receives the event change information.

[0080] In one embodiment, the preset instantiated object acts as a publisher and stores a data space, and the linked and bound page module acts as a subscriber and changes the data space by calling the subscription method;

[0081] Correspondingly, the transmission module 102 is further configured to transmit the change information of the data space to the linked and bound page module when any linked and bound page module calls the subscription method to change the data space.

[0082] In one embodiment, the delivery module 102 is specifically configured to:

[0083] When any page module bound by linkage calls the subscription method to change the data space, the broadcast method is called to trigger the change event, so as to obtain the event change information corresponding to the data space through the change event;

[0084] The linked and bound page modules are traversed, and the callback function of each page module is called in turn, so as to transmit the event change information to the linked and bound page modules through the callback function.

[0085] In one embodiment, the apparatus further comprises:

[0086] The establishment module is used to establish a subscription relationship between the linked and bound page module and the preset instantiation object during the initialization process of the preset instantiation object before creating at least one preset instantiation object in the memory.

[0087] In one embodiment, a module is established, specifically for:

[0088] Extracting dependent fields of the page modules in the data space according to the linked and bound page modules;

[0089] Determining the data linkage logic of the page module based on the dependency fields of the page module, wherein the data linkage logic is the logic for linking changes of data in the page module based on data changes in the data space;

[0090] During the initialization process of the preset instantiation object, a subscription relationship between the linked and bound page module and the preset instantiation object is established according to the data linkage logic of the page module.

[0091] In one embodiment, the apparatus further comprises:

[0092] A determination module, configured to determine, before creating at least one preset instantiation object in the memory, at least one linkage binding relationship between the page modules based on the data flow and dependency relationship between the page modules;

[0093] Correspondingly, the creation module 101 is further configured to create a preset instantiation object in memory for a linkage binding relationship.

[0094] In one embodiment, the linkage module 103 is specifically configured to:

[0095] After the linked and bound page modules receive the event change information, the event change parameters are extracted from the event change information according to the parameter parsing logic customized by each page module;

[0096] The data change in the corresponding page module is executed according to the event change parameter, so that the data change of the page module is linked with the event change parameter.

[0097] The present invention provides a data linkage device for page modules, which provides a subscription mode for page modules by instantiating objects. When the publisher's data structure changes, the linked and bound page modules execute corresponding data changes, which can ensure the consistency of each page module in the data linkage process. This process only requires the publisher to meet the data structure requirements, and does not require modification of the existing page structure. Personalized page modules can be customized, so that the page modules can be flexibly bound.

[0098] For the specific definition of the data linkage device of the page module, please refer to the definition of the intelligent question and answer method above, which will not be repeated here. Each module in the data linkage device of the above-mentioned page module can be implemented in whole or in part by software, hardware and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0099] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 9 As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the server side of a data linkage method of a page module.

[0100] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Figure 10 As shown. The computer device includes a processor, memory, network interface, display screen, and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps on the client side of a data linkage method for a page module.

[0101] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are performed:

[0102] Creating at least one preset instantiation object in memory, wherein the preset instantiation object is configured with a subscription method for being called by the linked binding page module;

[0103] When any page module bound by linkage calls the subscription method, the event change information triggered by the subscription method is passed to the page module bound by linkage;

[0104] After the linked and bound page module receives the event change information, it performs corresponding data changes according to the event change information.

[0105] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0106] Creating at least one preset instantiation object in memory, wherein the preset instantiation object is configured with a subscription method for being called by the linked binding page module;

[0107] When any page module bound by linkage calls the subscription method, the event change information triggered by the subscription method is passed to the page module bound by linkage;

[0108] After the linked and bound page module receives the event change information, it performs corresponding data changes according to the event change information.

[0109] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can be found in the relevant descriptions of the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0110] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0111] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0112] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A data linkage method for a page module, characterized in that: include: Creating at least one preset instantiation object in memory, wherein the preset instantiation object is configured with a subscription method for being called by the linked binding page module; When any page module bound by linkage calls the subscription method, the event change information triggered by the subscription method is passed to the page module bound by linkage; After the linked and bound page module receives the event change information, it performs corresponding data changes according to the event change information.

2. The data linkage method of the page module according to claim 1, characterized in that: The preset instantiated object acts as a publisher and stores a data space, and the linked and bound page module acts as a subscriber and changes the data space by calling the subscription method; Correspondingly, when any linked and bound page module calls the subscription method to change the data space, the change information of the data space is transmitted to the linked and bound page module.

3. The data linkage method of the page module according to claim 2, characterized in that: When any linked and bound page module calls the subscription method to change the data space, the change information of the data space is transmitted to the linked and bound page module, including: When any page module bound by linkage calls the subscription method to change the data space, the broadcast method is called to trigger the change event, so as to obtain the event change information corresponding to the data space through the change event; The linked and bound page modules are traversed, and the callback function of each page module is called in turn, so as to transmit the event change information to the linked and bound page modules through the callback function.

4. The data linkage method of the page module according to claim 1, characterized in that: Before creating at least one preset instantiation object in the memory, the method further includes: During the initialization process of the preset instantiation object, a subscription relationship is established between the linked and bound page module and the preset instantiation object.

5. The data linkage method of the page module according to claim 4, characterized in that: During the initialization process of the preset instantiation object, a subscription relationship is established between the linked and bound page module and the preset instantiation object, including: Extracting dependent fields of the page modules in the data space according to the linked and bound page modules; Determining the data linkage logic of the page module based on the dependency fields of the page module, wherein the data linkage logic is the logic for linking changes of data in the page module based on data changes in the data space; During the initialization process of the preset instantiation object, a subscription relationship between the linked and bound page module and the preset instantiation object is established according to the data linkage logic of the page module.

6. The data linkage method for page modules according to any one of claims 1 to 5, characterized in that: Before creating at least one preset instantiation object in the memory, the method further includes: Determine at least one linkage binding relationship between the page modules based on the data flow and dependency relationship between the page modules; Accordingly, for a linkage binding relationship, a preset instantiation object is created in memory.

7. The data linkage method for page modules according to any one of claims 1 to 5, characterized in that: After the linked and bound page module receives the event change information, executing corresponding data changes according to the event change information includes: After the linked and bound page modules receive the event change information, the event change parameters are extracted from the event change information according to the parameter parsing logic customized by each page module; The data change in the corresponding page module is executed according to the event change parameter, so that the data change of the page module is linked with the event change parameter.

8. A data linkage device for a page module, characterized in that: include: A creation module, configured to create at least one preset instantiation object in memory, wherein the preset instantiation object is configured with a subscription method for being called by the linked binding page module; A transmission module, configured to transmit the event change information triggered by the subscription method to the linked and bound page module when any linked and bound page module calls the subscription method; The linkage module is used to execute corresponding data changes according to the event change information after the linkage-bound page module receives the event change information.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the data linkage method for the page module according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the data linkage method of the page module as claimed in any one of claims 1 to 7 are implemented.

Images