Data processing method and device of management system and electronic equipment

Abstract

The invention provides a data processing method and device of a management system and electronic equipment. The method comprises the steps that a browser reads target state information in a data warehouse; if the state is the non-predetermined state, calling a data warehouse interface to send an HTTP menu request of menu data to a server; calling a data warehouse interface to store the menu data in a browser cache, and calling the data warehouse interface to modify the target state information into a predetermined state; and if the state is the preset state, calling the data warehouse interface in real time to obtain the menu data in the cache, and rendering a real-time display page based on the menu data. And if the menu data stored in the database is changed, the server informs the browser to send an HTTP menu request to the server to request the latest menu data. According to the scheme, the menu data acquisition request can be quickly responded, and the HTTP menu request quantity sent to the server by the browser is reduced; and when the menu data stored in the database is changed, the menu data cached at the browser end is updated in time.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, device and electronic equipment for a management system. Background Art

[0002] The management system usually has system menu data, and the menu data is used to display pages of multiple business nodes in the system.

[0003] Some large management systems often have the problem of slow page menu display during use, which seriously affects the user experience. Currently, there is no effective way to solve the problem of slow menu display in large management systems. Summary of the invention

[0004] This specification provides a data processing method, device and electronic device for a management system to solve the problem of slow display of page menus in large management systems.

[0005] To solve the above technical problems, the first aspect of the present specification provides a data processing method for a management system, comprising: a browser reads target state information in a data warehouse; when the target state information is in a non-predetermined state, the browser calls a backend interface in the data warehouse to send an HTTP menu request to a server; the HTTP menu request is used to enable the server to obtain menu data from a database, and use the menu data as feedback data of the HTTP menu request; the browser calls the backend interface in the data warehouse to store the menu data fed back by the server in the browser's cache, and calls the backend interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state; when the target state information is in a predetermined state, the browser calls the frontend interface in the data warehouse in real time to obtain the menu data in the cache, and renders a real-time display page of the management system based on the menu data; receives a change notification sent by the server; the change notification is sent to the browser in response to a change in the menu data in the database; in response to the change notification, calls the backend interface in the data warehouse to send an HTTP menu request to the server to request the menu data; and calls the backend interface in the data warehouse to modify the menu data stored in the browser cache according to the feedback data of the HTTP menu request.

[0006] In some embodiments, the method also includes: after the browser logs into the management system, calling the back-end interface in the data warehouse to send an HTTP menu request to the server for the first time to request menu data; receiving the menu data fed back by the server in response to the HTTP menu request; the browser calls the back-end interface in the data warehouse to store the menu data fed back by the server in the browser cache, and calls the back-end interface in the data warehouse to modify the target status information in the data warehouse to a predetermined status.

[0007] In some embodiments, the menu data sent by the server in response to the HTTP menu request sent by the browser is full menu data or partial menu data; in the case where the menu data sent by the server in response to the HTTP menu request sent by the browser is partial menu data, the method further includes: the browser splices the partial menu data with the partial menu data that has been cached; accordingly, the browser renders a real-time display page of the management system based on the spliced ​​menu data.

[0008] In some embodiments, the HTTP menu request includes the size of the available cache space; the size of the available cache space is used by the server to determine the width and / or depth of the menu sent to the browser.

[0009] In some embodiments, the method also includes: when the cache space is insufficient, deleting the menu data branch segments with lower access heat values ​​in the cached menu data; the menu data sent by the server in response to the HTTP menu request sent by the browser are the menu data branch segments, as well as the access heat values ​​corresponding to each menu data.

[0010] In some embodiments, the data warehouse is Vuex; the data warehouse Vuex is created by the following method: creating a state object state, a behavior object actions and an update object mutations; setting a data storage variable in the state object state, the data storage variable is used to store menu data and represent target state information; setting a first backend interface in the behavior object actions, the first backend interface is used to send an HTTP menu request to the server to request menu data, and receive feedback data from the server; setting a second backend interface in the update object mutations, the second backend interface is used to change the data stored in the data storage variable; setting the data acquisition interface getters of the data warehouse, the data acquisition interface getters is used by the front end to obtain the data stored in the browser cache menu data; accordingly, the browser reads the target state information in the data warehouse, including: the browser calls the data acquisition interface getters to obtain the value of the data storage variable in the state object state; the browser calls the back-end interface in the data warehouse to send an HTTP menu request to the server, including: the browser calls the first back-end interface to request menu data from the server, and calls the second back-end interface to modify the value of the data storage variable in the behavior object according to the return data of the first back-end interface; the browser calls the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and renders the real-time display page of the management system based on the menu data, including: the browser calls the data acquisition interface getters in real time to obtain the value of the data storage variable in the behavior object state, and renders the real-time display page of the management system based on the value.

[0011] In some embodiments, the method further includes: when the user logs out of the management system, the browser calls the second backend interface in the update object mutations to set the data storage variable to null.

[0012] The second aspect of the present specification provides a data processing method for a management system, including: receiving an HTTP menu request sent by a user client, the HTTP menu request being used to obtain menu data; in response to the HTTP menu request, obtaining menu data from a database, and using the menu data as feedback data for the HTTP menu request; monitoring data changes in the database; in the event of data changes in the database, determining a target user identifier involved in the data change; sending a change notification to a browser logged in by a target user identifier in a logged-in state; the change notification is used to enable the target user client to send an HTTP menu request for requesting menu data.

[0013] In some embodiments, in response to the HTTP menu request, menu data is obtained from a database and used as feedback data of the HTTP menu request, including: in response to the HTTP menu request sent by the browser, full menu data or partial menu data is obtained from a database and used as feedback data of the HTTP menu request.

[0014] In some embodiments, in response to the HTTP menu request, menu data is obtained from a database, and the menu data is used as feedback data of the HTTP menu request, including: in response to the HTTP menu request sent for the first time after the browser logs into the management system, menu data and the user's access heat value for each menu page in the full menu data are obtained from the database; according to the access heat value of each menu page, a target menu data branch whose access heat value reaches a first preset condition is determined; and the data of the target menu data branch is used as feedback data of the HTTP menu request.

[0015] In some embodiments, the data of the target menu data branch is used as feedback data of the HTTP menu request, including: determining whether each menu page on the target menu data branch meets a second preset condition based on the access heat value of each menu page, and taking the menu page with the longest access path that meets the second preset condition as the access depth of the target menu data branch; and taking each menu data on the access path of the access depth on the target menu data branch as feedback data of the HTTP menu request.

[0016] In some embodiments, in response to the HTTP menu request, menu data is obtained from a database, and the menu data is used as feedback data of the HTTP menu request, including: in response to the HTTP menu request, determining the width and depth of the user's access menu, the width being each menu data branch whose access heat value reaches a first preset condition, and the depth being the farthest menu page on a menu data branch whose access heat value reaches a second preset condition; determining the width and depth of a menu that matches the cache space size according to the cache space size carried in the HTTP menu request; and using the width and depth of the matching menu as feedback data of the HTTP menu request.

[0017] In some embodiments, in response to the HTTP menu request, menu data is obtained from a database, and the menu data is used as feedback data of the HTTP menu request, including: in response to the HTTP menu request sent for the first time after the browser is not logged in to the management system, the HTTP menu request sent for the first time after the browser is not logged in to the management system includes an identifier of a menu data branch; and the data of the menu data branch corresponding to the identifier is used as feedback data of the HTTP menu request.

[0018] The third aspect of the present specification provides a data processing device for a management system, including: a reading unit, used for a browser to read target state information in a data warehouse; a first processing unit, used for, when the target state information is not in a predetermined state, the browser calls a back-end interface in the data warehouse to send an HTTP menu request to a server; the HTTP menu request is used to enable the server to obtain menu data from a database, and use the menu data as feedback data for the HTTP menu request; the browser calls the back-end interface in the data warehouse to store the menu data fed back by the server in the browser's cache, and calls the back-end interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state ; a second processing unit, used for, when the target state information is a predetermined state, the browser calls the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and renders the real-time display page of the management system based on the menu data; a first receiving unit, used for receiving the change notification sent by the server; the change notification is sent to the browser in response to the change of the menu data in the database; a sending unit, used for, in response to the change notification, calling the back-end interface in the data warehouse to send an HTTP menu request to the server to request the menu data; a modifying unit, used for, according to the feedback data of the HTTP menu request, calling the back-end interface in the data warehouse to modify the menu data stored in the browser cache.

[0019] In some embodiments, the device also includes: a first calling unit, which is used to call the back-end interface in the data warehouse to send an HTTP menu request to the server for the first time to request menu data after the browser logs into the management system; a second receiving unit, which is used to receive the menu data fed back by the server in response to the HTTP menu request; and a third processing unit, which is used by the browser to call the back-end interface in the data warehouse to store the menu data fed back by the server in the browser cache, and call the back-end interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state.

[0020] In some embodiments, the menu data sent by the server in response to the HTTP menu request sent by the browser is full menu data or partial menu data; in the case where the menu data sent by the server in response to the HTTP menu request sent by the browser is partial menu data, the device also includes: a splicing unit, which is used for the browser to splice the partial menu data with the partial menu data that has been cached; accordingly, the browser renders the real-time display page of the management system based on the spliced ​​menu data.

[0021] In some embodiments, the HTTP menu request includes the size of the available cache space; the size of the available cache space is used by the server to determine the width and / or depth of the menu sent to the browser.

[0022] In some embodiments, the device also includes: a deletion unit, which is used to delete menu data branch segments with lower access heat values ​​in the cached menu data when the cache space is insufficient; the menu data sent by the server in response to the HTTP menu request sent by the browser are menu data branch segments, as well as the access heat values ​​corresponding to each menu data.

[0023] In some embodiments, the data warehouse is Vuex; the data warehouse Vuex is created in the following manner: create a state object state, a behavior object actions and an update object mutations; set a data storage variable in the state object state, the data storage variable is used to store menu data and represent target state information; set a first backend interface in the behavior object actions, the first backend interface is used to send an HTTP menu request to the server to request menu data, and receive feedback data from the server; set a second backend interface in the update object mutations, the second backend interface is used to change the data stored in the data storage variable; set the data acquisition interface getters of the data warehouse, the data acquisition interface getters is used by the front end to obtain the data stored in the browser cache menu data; accordingly, the browser reads the target state information in the data warehouse, including: the browser calls the data acquisition interface getters to obtain the value of the data storage variable in the state object state; the browser calls the back-end interface in the data warehouse to send an HTTP menu request to the server, including: the browser calls the first back-end interface to request menu data from the server, and calls the second back-end interface to modify the value of the data storage variable in the behavior object according to the return data of the first back-end interface; the browser calls the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and renders the real-time display page of the management system based on the menu data, including: the browser calls the data acquisition interface getters in real time to obtain the value of the data storage variable in the behavior object state, and renders the real-time display page of the management system based on the value.

[0024] In some embodiments, the device further includes: a second calling unit, configured to cause the browser to call a second backend interface in the update object mutations to set the data storage variable to null when the user logs out of the management system.

[0025] The fourth aspect of the present specification provides a data processing device for a management system, including: a third receiving unit, used to receive an HTTP menu request sent by a user client, wherein the HTTP menu request is used to obtain menu data; a feedback unit, used to respond to the HTTP menu request, obtain menu data from a database, and use the menu data as feedback data of the HTTP menu request; a monitoring unit, used to monitor data changes in the database; a determination unit, used to determine a target user identifier involved in the data change when data changes occur in the database; a notification unit, used to send a change notification to a browser logged in by a target user identifier in a logged-in state; the change notification is used to enable the target user client to send an HTTP menu request for requesting menu data.

[0026] In some embodiments, the feedback unit includes: a first feedback subunit, which is used to respond to an HTTP menu request sent by a browser, obtain full menu data or partial menu data from a database and use it as feedback data of the HTTP menu request.

[0027] In some embodiments, the feedback unit includes: an acquisition subunit, used to respond to the HTTP menu request sent for the first time after the browser logs into the management system, and obtain menu data and the user's access heat value for each menu page in the full menu data from the database; a first determination subunit, used to determine the target menu data branch whose access heat value meets the first preset condition based on the access heat value of each menu page; a second determination subunit, used to use the data of the target menu data branch as feedback data of the HTTP menu request.

[0028] In some embodiments, the second determination subunit includes: a third determination subunit, used to determine whether each menu page on the target menu data branch meets the second preset condition based on the access heat value of each menu page, and use the menu page with the longest access path that meets the second preset condition as the access depth of the target menu data branch; a fourth determination subunit, used to use each menu data on the access path of the access depth on the target menu data branch as feedback data of the HTTP menu request.

[0029] In some embodiments, the feedback unit includes: a fifth determination subunit, used to determine the width and depth of the user's access menu in response to the HTTP menu request, the width being each menu data branch whose access heat value reaches a first preset condition, and the depth being the farthest menu page on a menu data branch whose access heat value reaches a second preset condition; a sixth determination subunit, used to determine the width and depth of a menu that matches the cache space size based on the cache space size carried in the HTTP menu request; and a seventh determination subunit, used to use the width and depth of the matching menu as feedback data of the HTTP menu request.

[0030] In some embodiments, the feedback unit includes: a second feedback sub-unit, used to respond to the HTTP menu request sent for the first time after the browser logs in to the management system, and use the data of the menu data branch corresponding to the identifier as feedback data of the HTTP menu request; wherein, the HTTP menu request sent for the first time after the browser logs in to the management system includes the identifier of the menu data branch.

[0031] The fifth aspect of this specification provides an electronic device, comprising: a memory and a processor, the processor and the memory are communicatively connected to each other, the memory stores computer instructions, and the processor implements the data processing method of the management system described in any one of the first aspect or any one of the second aspect by executing the computer instructions.

[0032] A sixth aspect of the present specification provides a computer storage medium, wherein the computer storage medium stores computer program instructions, and when the computer program instructions are executed, the steps of the data processing method of the management system described in any one of the first aspect or any one of the second aspect are implemented.

[0033] A seventh aspect of the present specification provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the data processing method of the management system described in any one of the first aspect or any one of the second aspect.

[0034] The data processing method, device and electronic device of the management system provided in this specification are provided with a data warehouse on the browser, and the menu data is stored in the browser cache through the data warehouse. When the browser needs to access the menu page, it does not immediately generate an HTTP menu request to request menu data from the server, but reads the target state information in the data warehouse, and determines whether to generate an HTTP menu request to request menu data from the server according to the target state information. In the case that the menu data stored in the database changes, the server sends a notification to the browser, and the browser responds to the notification and sends an HTTP menu request to the server to request the latest menu data. This solution can directly obtain menu data from the browser cache and quickly respond to the menu data acquisition request, so that the page menu of the browser is displayed faster; this solution can also reduce the number of HTTP menu requests sent by the browser to the server, reduce the occupation of server resources, so that the server can have more resources to respond to the HTTP menu request of the browser, so that the server can quickly respond to the HTTP menu request of the browser, and the browser can obtain menu data immediately, so that the page menu of the browser is displayed faster; this solution can timely update the menu data cached by the browser when the menu data stored in the database changes, and will not make the user experience poor because the menu data is not updated in time. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0036] Figure 1 A schematic diagram of the data processing method of the management system provided in this specification;

[0037] Figure 2 Another schematic diagram of the data processing method of the management system provided in this specification;

[0038] Figure 3 A schematic diagram of menu data;

[0039] Figure 4 A schematic diagram of the method for creating a data warehouse;

[0040] Figure 5 A schematic diagram of a data warehouse;

[0041] Figure 6 Another schematic diagram of the data processing method of the management system provided in this specification;

[0042] Figure 7 A schematic diagram of the interaction between two ends of the data processing method of the management system provided in this specification;

[0043] Figure 8 Another schematic diagram of the data processing method of the management system provided in this specification;

[0044] Fig. 9 Another schematic diagram of the data processing method of the management system provided in this specification;

[0045] Fig.10 Another schematic diagram of the data processing method of the management system provided in this specification;

[0046] Fig.11 Another schematic diagram of the data processing method of the management system provided in this specification;

[0047] Fig.12 A schematic diagram of a data processing device of a management system provided in this specification;

[0048] Fig.13 Another schematic diagram of the data processing device of the management system provided in this specification;

[0049] Fig.14 This is a schematic diagram of the structure of the electronic device provided in this manual. DETAILED DESCRIPTION

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

[0051] It should be noted that the user-related information and data involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by relevant parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users or relevant parties to choose to authorize or refuse.

[0052] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0053] Large management systems usually have a large amount of system menu data, and the menu data is used to display pages of multiple business nodes in the management system.

[0054] The page display implementation process of the business node is usually that the client for displaying the page sends an HTTP menu request to the server of the management system, and the HTTP menu request is used to obtain the menu data of the management system; in response to the acquisition request, the server sends the menu data of the management system to the client via the network HTTP.

[0055] The inventors discovered that the implementation methods of these business node display pages will call the back-end interface to obtain menu data. Usually, large-scale management systems are jointly developed and maintained by multiple people in the R&D team. The R&D work of multiple business nodes may be assigned to multiple R&D personnel for parallel development or maintenance. They usually independently write the back-end interface code for calling menu data during the R&D and maintenance process. After development and maintenance by multiple people, the management system will have multiple back-end interfaces to obtain menu data. The amount of menu data in large-scale management systems is large, and obtaining menu data through HTTP menu requests will consume too many network resources. Multiple back-end interfaces continue to consume network resources when continuously obtaining menu data through HTTP menu requests, and also occupy more server resources. The above reasons lead to the problem of slow page menu display in large-scale management systems during use.

[0056] Based on the above analysis, this specification provides a data processing method for a management system. After the management system obtains menu data for the first time through an HTTP menu request, the method stores the menu data on the front end, and subsequently responds to HTTP menu requests from each business node to obtain menu data, and directly obtains the pre-stored menu data from the front end.

[0057] Management systems are usually able to display a large number of page menus. Page menus refer to the options or links provided to users for navigation and operation in the management system. Users can use these options or links to quickly access different parts of the management system or perform specific operations. The information of each page menu is stored in a database. When the browser requests menu data from the server, the server extracts the information of all page menus that the user can access from the database according to the user's permissions and feeds it back to the browser as menu data. The browser determines what content should be displayed after the user performs an operation based on the menu data.

[0058] The front end is a component in the browser that is related to user interaction. These components capture user operations and store display resources on the server according to the user's operation request so that the browser page can then display these display resources to the user. The above menu data acquisition request refers to: the display resources stored on the server by the components related to user interaction according to the user's operation request.

[0059] like Figure 1 As shown, the data processing method of the management system includes the following S11 to S13. The method can be used for user clients, which can be physical devices such as computers, tablets, and mobile terminals. Browsers are run on these physical devices, and users use the management system through browsers.

[0060] S11: The browser reads the target status information in the data warehouse.

[0061] This step may be executed in response to a user operating an option or link displayed on a management system page, or may be executed in response to reaching a rendering time.

[0062] The data warehouse includes the definition of data variables, the definition of front-end interfaces, and the definition of back-end interfaces. Among them, data variables are defined as menu data, the front-end interface is used to obtain menu data at the front end, and the back-end interface is used to obtain menu data from the server and assign it to data variables. The front-end interface cannot change menu data, but the back-end data can change menu data.

[0063] By setting up a data warehouse, developers and maintenance personnel can easily set up data transfer from the backend to the frontend. In addition to transferring menu data, the data warehouse can also be used to transfer other data. When there are many types of data that need to be transferred between the backend and the frontend, setting up a data warehouse can greatly simplify the logic, coding difficulty and workload of these data transfers.

[0064] The HTML file used to present the web page can usually be modified by the user on the browser side. For example, after the user opens the web page, he can right-click on the page and select "View Page Source" to open the source code view. In the source code view, the user can directly edit the HTML code and then use the browser to refresh the page to view the effect. The above-mentioned front-end interface can be directly called by the HTML file of the browser, while the back-end interface cannot be directly called by the HTML file. Therefore, even if the user modifies the HTML file, the menu data stored in the data warehouse cannot be modified, so that the content of the page that the user can access will not be deleted, and the user cannot add web pages that he cannot view by his authority. That is, by setting the front-end interface and the back-end interface, the accuracy and reliability of the user's access rights can also be guaranteed.

[0065] The target state information includes a predetermined state and a non-predetermined state. The predetermined state means that the browser has cached the menu data, and the non-predetermined state means that the browser has not cached the menu data.

[0066] S12: When the target state information is not in a predetermined state, the browser calls the back-end interface in the data warehouse to send an HTTP menu request to the server; the HTTP menu request is used to enable the server to obtain menu data from the database, and use the menu data as feedback data of the HTTP menu request; the browser calls the back-end interface in the data warehouse to store the menu data fed back by the server in the browser's cache, and calls the back-end interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state.

[0067] The relationship between the browser, server and database is shown in the figure below: Figure 2 shown.

[0068] Storing menu data in the browser's cache can improve the efficiency of the front-end in obtaining menu data.

[0069] In response to the HTTP menu request sent by the browser, the server can feedback the full amount of menu data at one time, and the browser caches the full amount of menu data, and clears the menu cache when the browser logs out. Feeding back the full amount of menu data at one time can greatly reduce the number of menu requests.

[0070] The full menu data mentioned in this specification refers to all menu data to which the user has access rights; the partial menu data mentioned in this specification refers to a portion of the full menu data. The partial menu data is less than the full menu data.

[0071] In response to the HTTP menu request sent by the browser, the server can also feed back part of the menu data at one time. The browser caches this part of the menu data, and when the menu page information not in the cached menu is requested, the HTTP menu request is sent to the server to request new menu data.

[0072] S13: When the target state information is a predetermined state, the browser calls the front-end interface in the data warehouse to obtain the menu data in the cache, and renders the display page of the management system in real time based on the menu data.

[0073] The above S11 to S13 may be steps executed in the background of the browser, that is, the user cannot modify the above S11 to S13 by modifying the HTML file of the web page.

[0074] In the case where the data warehouse is used to cache the menu data in the browser cache, if the data stored in the database changes and causes the page menu that the user can access to change, the browser cannot update the menu data in time. In this regard, the present solution further provides the following S14, S15 and S16.

[0075] S14: receiving a change notification sent by the server; the change notification is sent to the browser in response to a change in menu data in the database.

[0076] The server can monitor the data changes in the database. When the menu data and user authority data in the database change, the server can determine the set of users whose accessible page menus have changed, and actively send the latest menu data to these users.

[0077] S15: In response to the change notification, calling the backend interface in the data warehouse to send an HTTP menu request to the server to request menu data.

[0078] In response to the HTTP menu request, the server obtains menu data from a database and uses the menu data as feedback data of the HTTP menu request.

[0079] S16: According to the feedback data of the HTTP menu request, the back-end interface in the data warehouse is called to modify the menu data stored in the browser cache.

[0080] If the feedback data from the server is the changed data in the database, S16 can only call the backend interface to modify part of the data in the browser cache. The server only feeds back the changed data in the database to reduce the amount of data transmission between the server and the browser, and reduce the amount of server resources occupied.

[0081] If the feedback data of the server is the full amount of menu data in the database, S16 can call the back-end interface to use the feedback data of the server to cover the data in the browser cache. In this case, only a back-end interface can be set in the data warehouse to send HTTP menu requests to the server, reducing the coding difficulty of the management system.

[0082] Through the above S14, S15 and S16, the data change in the database can drive the browser to resend the HTTP menu request to the server to request the menu data, so that the browser can obtain the latest menu data in time and present it to the user.

[0083] The data processing method of the above management system is that a data warehouse is set on the browser, and the menu data is stored in the browser cache through the data warehouse. When the browser needs to access the menu page, it does not immediately generate an HTTP menu request to request menu data from the server, but reads the target state information in the data warehouse, and determines whether to generate an HTTP menu request to request menu data from the server according to the target state information. In the case that the menu data stored in the database changes, the server sends a notification to the browser, and the browser responds to the notification and sends an HTTP menu request to the server to request the latest menu data. This solution can directly obtain menu data from the browser cache and quickly respond to the menu data acquisition request, so that the browser page menu is displayed faster; this solution can also reduce the number of HTTP menu requests sent by the browser to the server, reduce the occupation of server resources, so that the server can have more resources to respond to the browser's HTTP menu request, so that the server can quickly respond to the browser's HTTP menu request, and the browser can obtain menu data immediately, so that the browser page menu is displayed faster; this solution can timely update the menu data cached on the browser side when the menu data stored in the database changes, and will not cause users to have a poor experience due to the failure to update the menu data in time.

[0084] There are embodiments of caching menu data in the browser in the prior art. However, the implementation method of the prior art is usually that after the browser sends an HTTP menu request to the server to request menu data, the server obtains the menu data from the database, feeds back the menu data to the browser, and sets a validity period for the menu data. The browser stores the menu data locally in the browser, and after the validity period expires, the browser sends an HTTP menu request to the server again to request the menu data.

[0085] There are already embodiments of using a data warehouse to cache data in the prior art, but the prior art usually stores data on a server through a data warehouse. According to the prior art, when a user operates a browser page to generate a menu data acquisition request, the browser will generate an HTTP menu request to request menu data from the server. The server obtains the menu data from the database and sends the menu data to the browser as feedback data of the HTTP menu request. The browser determines the page resources to be displayed based on the menu data. In this way, the browser still needs to frequently send HTTP menu requests to the server, which occupies a large amount of server resources, that is, the technical problem to be solved by this solution still exists.

[0086] Due to reasons such as expansion, optimization, and authority changes of the management system, the data stored in the database may change during the user's use of the management system, thereby changing the page menu that the user can access. In this regard, if the menu changes are caused by reasons such as expansion and optimization of the management system, the prior art usually chooses to update the database and restart the server at a certain time, which will cause the management system to be unavailable for a period of time; if the menu changes are caused by changes in user authority, the prior art frequently or regularly sends HTTP menu requests to the server to obtain menu data, so the prior art can enable the browser to promptly update the menu information that can be displayed after the database updates the menu.

[0087] In some embodiments, the data processing method of the management system also includes the following S14, S15 and S16.

[0088] S14: After the browser logs in to the management system, it calls the backend interface in the data warehouse to send an HTTP menu request to the server for the first time to request menu data.

[0089] In response to the HTTP menu request, the server obtains menu data from a database and uses the menu data as feedback data of the HTTP menu request.

[0090] S15: Receive menu data fed back by the server in response to the HTTP menu request.

[0091] S16: The browser calls the backend interface in the data warehouse to store the menu data fed back by the server in the browser cache, and calls the backend interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state.

[0092] The above S14 to S16 define that the menu data initially cached in the browser cache may be obtained in response to the first request to the server after logging into the management system.

[0093] In addition to the methods described in S14 to S16 above, the menu data initially cached in the browser cache may also be obtained by other methods.

[0094] In some embodiments, the menu data sent by the server in response to the HTTP menu request sent by the browser is partial menu data, and the browser concatenates the partial menu data with the partial menu data that has been cached. Figure 3is a schematic diagram of menu data. Each identifier in the tree structure is a menu data. A menu data corresponds to a link (i.e., a page) of the management system. A, B, C, and D are the four menu pages that can be entered first after logging in. Clicking the link under page A can enter pages A1, A2, and A3. Clicking the link under page A1 can enter pages A11, A12, and A13, and so on. Figure 3 The menu data shown. After the browser logs in to the management system, the server can first feedback the menu data of menu data branch A (i.e., the content in the upper dotted box). If the user visits page B while using the management system, an HTTP menu request can be resent to the server to request menu data, and the server can feedback the menu data of menu data branch B (i.e., the content in the lower dotted box). The browser can splice the contents of the two dotted boxes to obtain a large menu data. Accordingly, the browser renders the real-time display page of the management system based on the spliced ​​menu data.

[0095] In some embodiments, the HTTP menu request includes the size of the available cache space; the size of the available cache space is used by the server to determine the width and / or depth of the menu sent to the browser. The width of the menu sent to the browser may be determined based on the number of links under the menu page that the browser is currently accessing. For example, if the menu page that is currently accessed is the homepage, then Figure 3 The menu shown in the figure can send a menu with a width of 3 to the browser. The depth of the menu sent to the browser can be determined based on the number of clickable accesses under a link on the current page to be accessed, for example, based on Figure 3 In the menu shown, the depth of menu data branch A is 3, the depth of menu data branch C is 2, the depth of menu data A3 is 2, and the depth of menu data A31 is 3.

[0096] The server can pre-set the corresponding relationship between the size of the available cache space and the width and depth of the menu, and determine the menu data branch or menu data branch segment to be fed back according to the size of the available cache space and the page that the browser is currently accessing (the HTTP menu request also includes the identifier of the page that the browser is currently accessing), or calculate the menu data branch or menu data branch segment that matches the size of the available cache space according to a preset algorithm. For example, after the browser logs in to the management system, if the available cache space is large, the full amount of menu data can be fed back to the browser; if the available cache space is small, only part of the menu data branch can be fed back, for example, only the menu data branch in the upper dotted box can be fed back. In the case where the depth of a menu data branch is deep, only part of the menu data branch segment on a menu data branch can also be fed back. For example, if the page to be accessed is A3, only the menu data A3 and the menu data A31 and A32 under its branches can be fed back; if the page to be accessed is A, only the menu data A and the menu data A1, A2, A3 under its branches can be fed back, or the menu data A1 can not be fed back.

[0097] In some embodiments, the menu data sent by the server in response to the HTTP menu request sent by the browser are menu data branch segments and access heat values ​​corresponding to each menu data. In the case of insufficient cache space, the browser can delete the menu data branch segments with lower access heat values ​​in the cached menu data. The access heat value can specifically be the user's historical access frequency, or the access frequency in the most recent predetermined time period.

[0098] In some embodiments, Figure 4 As shown, the data warehouse is Vuex, and the data warehouse Vuex can be created by the methods described in the following S01 to S05.

[0099] S01: Create state object state, behavior object actions and update object mutations.

[0100] S02: Setting a data storage variable in the state object state, wherein the data storage variable is used to store menu data and represent target state information.

[0101] S03: Setting a first backend interface in the action object actions, wherein the first backend interface is used to send an HTTP menu request to a server to request menu data, and receive feedback data from the server.

[0102] S04: Setting a second backend interface in the update object mutations, wherein the second backend interface is used to change the data stored in the data storage variable.

[0103] S05: Setting the data acquisition interface getters of the data warehouse, wherein the data acquisition interface getters are used by the front end to acquire the menu data stored in the browser cache.

[0104] like Figure 5 As shown, a menuData variable is created in the state object state to represent the target state information and to store menu data. The menuData variable is a data storage variable. The data in the menuData variable is stored in the browser's cache. The value of the menuData variable is initialized to null. After the browser requests the menu data, the menu data is stored in the menuData variable and then in the browser cache. The value of the menuData variable is null, which corresponds to the target state information being a non-predetermined state. The value of the menuData variable is not null, which corresponds to the target state information being a predetermined state.

[0105] An asynchronous method actMenuData is set in the action object actions to send an HTTP menu request to the server to request menu data and receive feedback data from the server. The asynchronous method actMenuData is the first backend interface mentioned above.

[0106] In the update object mutations, set a method muMenuData to change the value of the menuData variable in the state object state, that is, to modify the menu data.

[0107] You can set the time interval for page rendering. When the time interval is reached, the page of the management system is rendered according to the value of the data storage variable menuData in the state object state. This process can be used as real-time call and real-time rendering.

[0108] After the browser logs in to the management system, the first rendering time arrives, and the browser calls the data acquisition interface getters to obtain the value of the data storage variable menuData in the behavior state object state, and the result is null. In this case, the browser calls the first backend interface actMenuData in the behavior object actions to send an HTTP menu request to the server to request menu data, and receives feedback data from the server; then, based on the return data obtained by the first backend interface actMenuData, the second backend interface muMenuData in the update object mutations is called to change the value of the data storage variable menuData in the state object state.

[0109] When the next rendering moment comes, if the value of the data storage variable menuData in the state object state is not null, the browser will directly call the data acquisition interface getters to obtain the value of the data storage variable in the behavior object state, and render the real-time display page of the management system based on these values.

[0110] When the user logs out of the management system, the browser calls the second backend interface in the update object mutations to set the data storage variable to null. Then the browser page will no longer display the management system page, and it is impossible to make the browser display the management system page by changing the HTML file of the page.

[0111] This specification also provides a data processing method for a management system, which can be used for a server of the management system. The server is connected to the user client for communication, and the user uses the management system through a browser running on the user client. Figure 6 and Figure 7 As shown, the method includes the following S21 to S25.

[0112] S21: receiving an HTTP menu request sent by a user client, wherein the HTTP menu request is used to obtain menu data.

[0113] S22: In response to the HTTP menu request, menu data is acquired from a database, and the menu data is used as feedback data of the HTTP menu request.

[0114] In response to the HTTP menu request sent by the browser, S22 may obtain the full menu data or part of the menu data from the database and use it as feedback data of the HTTP menu request.

[0115] S23: Monitor data changes in the database.

[0116] S24: When data changes occur in the database, determine the target user identifier involved in the data change.

[0117] Since the management system usually has many users and the user permissions are relatively complex, three data tables are usually set up in the management system's database: the menu table, the permission table, and the permission-menu correspondence table. The menu table is used to record the identifiers of all menu data in the management system, the permission table is used to record the permission identifier corresponding to the user identifier, and the permission-menu correspondence table is used to record the correspondence between the permission identifier and the menu data identifier. When the data in the above three data tables is modified or deleted, the user permissions may change. For this, the server needs to determine the identifier of the target user corresponding to the modified or deleted data.

[0118] S25: Send a change notification to the browser logged in by the target user identification in the logged-in state; the change notification is used to make the target user client send an HTTP menu request for requesting menu data.

[0119] If the target user ID corresponding to the modified or deleted data is in a logged-in state, the menu data may have been cached on the user's client browser. If the cached data is not changed, the menu data will be inconsistent with the database. To this end, the server can actively send a change notification to the browser used by the target user ID in the logged-in state to log in to the management system.

[0120] After the browser of the user client receives the change notification, in response to the change notification, the browser will call the back-end interface in the data warehouse to send an HTTP menu request to the server to request menu data, and call the back-end interface in the data warehouse with the feedback data of the HTTP menu request to modify the menu data stored in the browser cache.

[0121] In response to the HTTP menu request sent by the browser, the full amount of menu data or part of the menu data is obtained from the database and used as feedback data of the HTTP menu request.

[0122] In some embodiments, Figure 8 As shown, S22 may include the following S221 to S223.

[0123] S221: In response to the first HTTP menu request sent by the browser after logging into the management system, menu data and the user's access heat value for each menu page in the full menu data are obtained from the database.

[0124] The access heat value may specifically be the user's historical access frequency, or the access frequency in a recent predetermined time period.

[0125] S222: Determine, according to the access heat values ​​of each menu page, a target menu data branch whose access heat reaches a first preset condition.

[0126] Menu data branch refers to the access path corresponding to each menu page that can be accessed after logging into the management system. For example, Figure 3 The menu shown has four menu data branches, namely A, B, C and D. The target menu data branch is one of the menu data branches.

[0127] The target menu data branch whose access heat reaches the first preset condition may refer to the menu data branch where the menu data whose access heat value reaches the preset threshold is located; it may also be the menu data branch where the first N (N is a positive integer) menu data with the highest access heat value are located; it may also be the menu data branch where the total access volume of multiple menu data on the menu data branch reaches the preset heat value; it may also be a menu data branch composed of menu data of other situations, which will not be listed one by one in this manual.

[0128] S223: Use the data of the target menu data branch as feedback data of the HTTP menu request.

[0129] Through the above S221 to S223, after the browser logs into the management system and sends the HTTP menu request for the first time, the server can feedback the menu data branch that the user visits most frequently, instead of feedback the full amount of menu data. If the menu data volume of the management system is large, this processing method can reduce the menu data sent by the server to the browser, reducing the cache pressure of the browser.

[0130] For example, when user M uses a bank's management system, he usually only uses the "loan" function. After the browser logs into the bank's management system, the server can only send menu data related to the loan function to the browser. If the server sends menu data for other functions (such as funds, precious metal purchases) to the browser, they are rarely used, so it is easy to waste cache if the browser caches these menu data.

[0131] In some embodiments, Fig. 9 As shown, S223 may include the following S2231 and S2232.

[0132] S2231: Determine whether each menu page on the target menu data branch meets a second preset condition according to the access heat value of each menu page, and use the menu page with the longest access path that meets the second preset condition as the access depth of the target menu data branch.

[0133] The target menu data branch may be each selectable menu data branch after logging into the management system, or may be the menu data branch where the page currently accessed by the user is located.

[0134] S2232: Use each menu data on the access path of the access depth on the target menu data branch as feedback data of the HTTP menu request.

[0135] The menu page meets the second preset condition, which may mean that the access popularity value of the menu page reaches the preset threshold; it may also mean that the menu page is among the top N (N is a positive integer) menu pages with the highest access popularity values; it may also be a menu data branch composed of menu data of other situations, which will not be listed one by one in this manual.

[0136] by Figure 3 Taking the menu shown as an example, if the menu data B, B1, and B11 all meet the second preset condition, the access depth is B11, and the menu data B, B1, and B11 can be fed back; if only the menu data B and B1 meet the second preset condition, and B11 does not meet the second preset condition, the menu data B and B1 can be fed back.

[0137] Through the above S2231 to S2232, after the browser logs into the management system and sends the HTTP menu request for the first time, the server can feedback to the browser the menu data branch "segment" consisting of some menu data that users visit more frequently, instead of feedback the full amount of menu data or the entire menu data branch. For the management system with a large amount of menu data, especially when the menu data branch is long, this processing method can reduce the menu data sent by the server to the browser, reducing the cache pressure of the browser.

[0138] In some embodiments, Fig.10 As shown, S22 may include the following S224 to S226.

[0139] S224: In response to the HTTP menu request, determine the width and depth of the user's access menu, where the width refers to the menu data branches whose access heat values ​​reach a first preset condition, and the depth refers to the menu page with the longest access path among the menu pages whose access heat values ​​reach a second preset condition on a menu data branch.

[0140] The menu data branches whose access heat reaches the first preset condition may refer to the menu data branch where the menu data whose access heat value reaches the preset threshold is located; it may also be the menu data branch where the first N (N is a positive integer) menu data with the highest access heat value are located; it may also be the menu data branch where the total access volume of multiple menu data on the menu data branch reaches the preset heat value; it may also be a menu data branch composed of menu data of other situations, which will not be listed one by one in this manual.

[0141] The menu page meets the second preset condition, which may mean that the access popularity value of the menu page reaches the preset threshold; it may also mean that the menu page is among the top N (N is a positive integer) menu pages with the highest access popularity values; it may also be a menu data branch composed of menu data of other situations, which will not be listed one by one in this manual.

[0142] S225: Determine the width and depth of the menu that matches the cache space size according to the cache space size carried in the HTTP menu request.

[0143] S226: Using the width and depth of the matching menu as feedback data of the HTTP menu request.

[0144] The server can pre-set the corresponding relationship between the size of the available cache space and the width and depth of the menu, and determine the menu data branch or menu data branch segment to be fed back according to the size of the available cache space and the page that the browser is currently accessing (the HTTP menu request also includes the identifier of the page that the browser is currently accessing), or calculate the menu data branch or menu data branch segment that matches the size of the available cache space according to a preset algorithm. For example, after the browser logs in to the management system, if the available cache space is large, the full amount of menu data can be fed back to the browser; if the available cache space is small, only part of the menu data branch can be fed back, for example, only the menu data branch in the upper dotted box can be fed back. In the case where the depth of a menu data branch is deep, only part of the menu data branch segment on a menu data branch can also be fed back. For example, if the page to be accessed is A3, only the menu data A3 and the menu data A31 and A32 under its branches can be fed back; if the page to be accessed is A, only the menu data A and the menu data A1, A2, A3 under its branches can be fed back, or the menu data A1 can not be fed back.

[0145] Through the above S224 to S226, it is possible to flexibly set which menu data branches are fed back, and only part of each menu data branch can be fed back. This allows for flexible feedback of multiple menu data branches to meet users' diverse access needs, while reducing the amount of menu data sent by the server to the browser, thereby reducing the browser's cache pressure.

[0146] In some embodiments, Fig.11 As shown, S22 may include S227 and S228 as follows.

[0147] S227: Responding to the HTTP menu request sent for the first time after the browser logs into the management system, the HTTP menu request sent for the first time after the browser logs into the management system includes an identifier of a menu data branch.

[0148] The identifier of the menu data branch can be used to indicate that a specific menu data branch is included, and the specific menu data branch includes a menu page that the user wants to access.

[0149] S228: Use the data of the menu data branch corresponding to the identifier as feedback data of the HTTP menu request.

[0150] The server can directly feed back the menu data on a specific menu data branch to the browser, or it can use the menu data branch corresponding to the identifier as the target menu branch and use any of the above methods to determine the menu data fed back to the user, such as using Figure 8 , Fig. 9 , Fig.10 The method shown determines the menu data fed back to the browser.

[0151] For example, Figure 3 As shown, the user currently visits page A3, and the server can feedback the menu data branch corresponding to A3 to the browser, that is, feedback menu data A31, A32. The server can also use A3 as the target menu branch and use any of the above methods to determine the menu data fed back to the user.

[0152] The browser side can splice the menu data branch fed back by the server this time with the already cached menu data. For a detailed description of splicing, please refer to other parts of this manual.

[0153] This specification provides a data processing device for a management system, which can be used to implement Figure 1 The data processing method of the management system shown in FIG. Fig.12 As shown, the device includes a reading unit 11, a first processing unit 12, a second processing unit 13, a first receiving unit 14, a sending unit 15 and a modifying unit 16.

[0154] The reading unit 11 is used for the browser to read the target state information in the data warehouse.

[0155] The first processing unit 12 is used for, when the target state information is not in a predetermined state, the browser calls the back-end interface in the data warehouse to send an HTTP menu request to the server; the HTTP menu request is used for the server to obtain menu data from the database, and use the menu data as feedback data of the HTTP menu request; the browser calls the back-end interface in the data warehouse to store the menu data fed back by the server in the browser's cache, and calls the back-end interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state.

[0156] The second processing unit 13 is used for, when the target state information is a predetermined state, for the browser to call the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and to render a real-time display page of the management system based on the menu data.

[0157] The first receiving unit 14 is used to receive a change notification sent by the server; the change notification is sent to the browser in response to a change in the menu data in the database.

[0158] The sending unit 15 is used for sending an HTTP menu request to the server to request menu data in response to the change notification by calling the backend interface in the data warehouse.

[0159] The modification unit 16 is used to call the back-end interface in the data warehouse to modify the menu data stored in the browser cache according to the feedback data of the HTTP menu request.

[0160] In some embodiments, the device also includes: a first calling unit, which is used to call the back-end interface in the data warehouse to send an HTTP menu request to the server for the first time to request menu data after the browser logs into the management system; a second receiving unit, which is used to receive the menu data fed back by the server in response to the HTTP menu request; and a third processing unit, which is used by the browser to call the back-end interface in the data warehouse to store the menu data fed back by the server in the browser cache, and call the back-end interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state.

[0161] In some embodiments, the menu data sent by the server in response to the HTTP menu request sent by the browser is full menu data or partial menu data; in the case where the menu data sent by the server in response to the HTTP menu request sent by the browser is partial menu data, the device also includes: a splicing unit, which is used for the browser to splice the partial menu data with the partial menu data that has been cached; accordingly, the browser renders the real-time display page of the management system based on the spliced ​​menu data.

[0162] In some embodiments, the HTTP menu request includes the size of the available cache space; the size of the available cache space is used by the server to determine the width and / or depth of the menu sent to the browser.

[0163] In some embodiments, the device also includes: a deletion unit, which is used to delete menu data branch segments with lower access heat values ​​in the cached menu data when the cache space is insufficient; the menu data sent by the server in response to the HTTP menu request sent by the browser are menu data branch segments, as well as the access heat values ​​corresponding to each menu data.

[0164] In some embodiments, the data warehouse is Vuex; the data warehouse Vuex is created in the following manner: create a state object state, a behavior object actions and an update object mutations; set a data storage variable in the state object state, the data storage variable is used to store menu data and represent target state information; set a first backend interface in the behavior object actions, the first backend interface is used to send an HTTP menu request to the server to request menu data, and receive feedback data from the server; set a second backend interface in the update object mutations, the second backend interface is used to change the data stored in the data storage variable; set the data acquisition interface getters of the data warehouse, the data acquisition interface getters is used by the front end to obtain the data stored in the browser cache menu data; accordingly, the browser reads the target state information in the data warehouse, including: the browser calls the data acquisition interface getters to obtain the value of the data storage variable in the state object state; the browser calls the back-end interface in the data warehouse to send an HTTP menu request to the server, including: the browser calls the first back-end interface to request menu data from the server, and calls the second back-end interface to modify the value of the data storage variable in the behavior object according to the return data of the first back-end interface; the browser calls the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and renders the real-time display page of the management system based on the menu data, including: the browser calls the data acquisition interface getters in real time to obtain the value of the data storage variable in the behavior object state, and renders the real-time display page of the management system based on the value.

[0165] In some embodiments, the device further includes: a second calling unit, configured to cause the browser to call a second backend interface in the update object mutations to set the data storage variable to null when the user logs out of the management system.

[0166] This specification provides a data processing device for a management system, which can be used to implement Figure 6 The data processing method of the management system shown in FIG. Fig.13 As shown, the device includes a third receiving unit 21, a feedback unit 22, a monitoring unit 23, a determining unit 24 and a notifying unit 25.

[0167] The third receiving unit 21 is used to receive an HTTP menu request sent by a user client, where the HTTP menu request is used to obtain menu data.

[0168] The feedback unit 22 is used for acquiring menu data from a database in response to the HTTP menu request, and using the menu data as feedback data of the HTTP menu request.

[0169] The monitoring unit 23 is used to monitor the data changes in the database.

[0170] The determination unit 24 is used to determine the target user identifier involved in the data change when there is a data change in the database.

[0171] The notification unit 25 is used to send a change notification to the browser logged in by the target user identification in the login state; the change notification is used to make the target user client send an HTTP menu request for requesting menu data.

[0172] In some embodiments, the feedback unit includes: a first feedback subunit, which is used to respond to an HTTP menu request sent by a browser, obtain full menu data or partial menu data from a database and use it as feedback data of the HTTP menu request.

[0173] In some embodiments, the feedback unit includes: an acquisition subunit, used to respond to the HTTP menu request sent for the first time after the browser logs into the management system, and obtain menu data and the user's access heat value for each menu page in the full menu data from the database; a first determination subunit, used to determine the target menu data branch whose access heat value meets the first preset condition based on the access heat value of each menu page; a second determination subunit, used to use the data of the target menu data branch as feedback data of the HTTP menu request.

[0174] In some embodiments, the second determination subunit includes: a third determination subunit, used to determine whether each menu page on the target menu data branch meets the second preset condition based on the access heat value of each menu page, and use the menu page with the longest access path that meets the second preset condition as the access depth of the target menu data branch; a fourth determination subunit, used to use each menu data on the access path of the access depth on the target menu data branch as feedback data of the HTTP menu request.

[0175] In some embodiments, the feedback unit includes: a fifth determination subunit, used to determine the width and depth of the user's access menu in response to the HTTP menu request, the width being each menu data branch whose access heat value reaches a first preset condition, and the depth being the farthest menu page on a menu data branch whose access heat value reaches a second preset condition; a sixth determination subunit, used to determine the width and depth of a menu that matches the cache space size based on the cache space size carried in the HTTP menu request; and a seventh determination subunit, used to use the width and depth of the matching menu as feedback data of the HTTP menu request.

[0176] In some embodiments, the feedback unit includes: a second feedback sub-unit, used to respond to the HTTP menu request sent for the first time after the browser logs in to the management system, and use the data of the menu data branch corresponding to the identifier as feedback data of the HTTP menu request; wherein, the HTTP menu request sent for the first time after the browser logs in to the management system includes the identifier of the menu data branch.

[0177] The description and functions of the above-mentioned devices can be understood by referring to the data processing method part of the management system, and will not be repeated here.

[0178] The embodiment of the present invention further provides an electronic device, which may be the user client running a browser, or a server. Fig.14 As shown, the electronic device may include a processor 1401 and a memory 1402, wherein the processor 1401 and the memory 1402 may be connected via a bus or other means. Fig.14 The example of connecting through bus is taken in the following.

[0179] The processor 1401 may be a central processing unit (CPU). The processor 1401 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0180] The memory 1402 is a non-transitory computer-readable storage medium that can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the data processing method of the management system in the embodiment of the present invention (for example, Fig.12The reading unit 11, the first processing unit 12, the second processing unit 13, the first receiving unit 14, the sending unit 15 and the modifying unit 16 shown in Fig.13 The processor 1401 executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory 1402, that is, the data processing method of the management system in the above method embodiment is implemented.

[0181] The memory 1402 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required by at least one function; the data storage area may store data created by the processor 1401, etc. In addition, the memory 1402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 1402 may optionally include a memory remotely arranged relative to the processor 1401, and these remote memories may be connected to the processor 1401 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0182] The one or more modules are stored in the memory 1402, and when executed by the processor 1401, the following is performed: Figure 1 or Figure 6 The data processing method of the management system in the illustrated embodiment.

[0183] The specific details of the above electronic device can be understood by referring to the corresponding descriptions and effects in the method embodiment, and will not be repeated here.

[0184] The present specification also provides a computer storage medium, wherein the computer storage medium stores computer program instructions, and when the computer program instructions are executed, the steps of the data processing method of the management system are implemented.

[0185] The present specification also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the steps of the data processing method of the management system are implemented.

[0186] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0187] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from other embodiments.

[0188] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions.

[0189] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0190] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute certain parts of the methods of each implementation method of the present application.

[0191] The present application can be used in many general or special computer system environments or configurations, such as personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0192] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0193] Although the present application has been described through embodiments, those skilled in the art will appreciate that there are many modifications and variations to the present application without departing from the spirit of the present application, and it is intended that the appended claims include these modifications and variations without departing from the spirit of the present application.

Claims

1. A data processing method for a management system, characterized in that: include: The browser reads the target status information in the data warehouse; In the case where the target state information is not in a predetermined state, the browser calls the backend interface in the data warehouse to send an HTTP menu request to the server; the HTTP menu request is used to enable the server to obtain menu data from the database, and use the menu data as feedback data of the HTTP menu request; the browser calls the backend interface in the data warehouse to store the menu data fed back by the server in the browser's cache, and calls the backend interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state; When the target state information is a predetermined state, the browser calls the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and renders a real-time display page of the management system based on the menu data; Receiving a change notification sent by a server; the change notification is sent to a browser in response to a change in menu data in a database; In response to the change notification, calling a backend interface in the data warehouse to send an HTTP menu request to a server to request menu data; According to the feedback data of the HTTP menu request, the back-end interface in the data warehouse is called to modify the menu data stored in the browser cache.

2. The method according to claim 1, characterized in that: The method further comprises: After the browser logs in to the management system, it calls the back-end interface in the data warehouse to send an HTTP menu request to the server for the first time to request menu data; Receiving menu data fed back by the server in response to the HTTP menu request; The browser calls the backend interface in the data warehouse to store the menu data fed back by the server in the browser cache, and calls the backend interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state.

3. The method according to claim 1, characterized in that The menu data sent by the server in response to the HTTP menu request sent by the browser is the full menu data or partial menu data; In the case where the menu data sent by the server in response to the HTTP menu request sent by the browser is partial menu data, the method further comprises: the browser splicing the partial menu data with the partial menu data that has been cached; Accordingly, the browser renders a real-time display page of the management system based on the spliced ​​menu data.

4. The method according to claim 1, characterized in that The HTTP menu request includes the size of the available cache space; the size of the available cache space is used by the server to determine the width and / or depth of the menu sent to the browser.

5. The method according to claim 1, characterized in that The method further comprises: When the cache space is insufficient, the menu data branch segments with lower access heat values ​​in the cached menu data are deleted; the menu data sent by the server in response to the HTTP menu request sent by the browser are the menu data branch segments and the access heat values ​​corresponding to each menu data.

6. The method according to claim 1, characterized in that The data warehouse is Vuex; the data warehouse Vuex is created by the following method: Create state object state, behavior object actions and update object mutations; Setting a data storage variable in the state object state, the data storage variable is used to store menu data and represent target state information; A first backend interface is set in the action object actions, wherein the first backend interface is used to send an HTTP menu request to a server to request menu data, and receive feedback data from the server; Setting a second backend interface in the update object mutations, wherein the second backend interface is used to change the data stored in the data storage variable; Set the data acquisition interface getters of the data warehouse, and the data acquisition interface getters are used by the front end to obtain the menu data stored in the browser cache; Accordingly, The browser reads the target state information in the data warehouse, including: the browser calls the data acquisition interface getters to obtain the value of the data storage variable in the state object state; The browser calls the backend interface in the data warehouse to send an HTTP menu request to the server, including: the browser calls the first backend interface to request menu data from the server, and calls the second backend interface to modify the value of the data storage variable in the behavior object according to the return data of the first backend interface; The browser calls the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and renders the real-time display page of the management system based on the menu data, including: the browser calls the data acquisition interface getters in real time to obtain the value of the data storage variable in the behavior object state, and renders the real-time display page of the management system based on the value.

7. The method according to claim 6, characterized in that The method further comprises: When the user logs out of the management system, the browser calls the second backend interface in the update object mutations to set the data storage variable to null.

8. A data processing method for a management system, characterized in that: include: Receiving an HTTP menu request sent by a user client, wherein the HTTP menu request is used to obtain menu data; In response to the HTTP menu request, menu data is acquired from a database, and the menu data is used as feedback data of the HTTP menu request; Monitor data changes in the database; In the event of a data change in the database, determine the target user ID involved in the data change; A change notification is sent to a browser logged in by a target user identification in a logged-in state; the change notification is used to enable the target user client to send an HTTP menu request for requesting menu data.

9. The method according to claim 8, characterized in that In response to the HTTP menu request, menu data is obtained from a database, and the menu data is used as feedback data of the HTTP menu request, including: In response to the HTTP menu request sent by the browser, the full amount of menu data or part of the menu data is obtained from the database and used as feedback data of the HTTP menu request.

10. The method according to claim 8, characterized in that In response to the HTTP menu request, menu data is obtained from a database, and the menu data is used as feedback data of the HTTP menu request, including: In response to the first HTTP menu request sent by the browser after logging into the management system, menu data and the user's access heat value for each menu page in the full menu data are obtained from the database; Determine, according to the access heat values ​​of each menu page, a target menu data branch whose access heat value reaches a first preset condition; The data of the target menu data branch is used as feedback data of the HTTP menu request.

11. The method according to claim 10, characterized in that Using the data of the target menu data branch as feedback data of the HTTP menu request includes: Determining whether each menu page on the target menu data branch meets a second preset condition according to the access heat value of each menu page, and taking the menu page with the longest access path that meets the second preset condition as the access depth of the target menu data branch; Each menu data on the access path of the access depth on the target menu data branch is used as feedback data of the HTTP menu request.

12. The method according to claim 8, characterized in that In response to the HTTP menu request, menu data is obtained from a database, and the menu data is used as feedback data of the HTTP menu request, including: In response to the HTTP menu request, determining the width and depth of the user's access menu, wherein the width is each menu data branch whose access heat value reaches a first preset condition, and the depth is the farthest menu page on a menu data branch whose access heat value reaches a second preset condition; Determining the width and depth of a menu that matches the cache space size according to the cache space size carried in the HTTP menu request; The width and depth of the matched menu are used as feedback data of the HTTP menu request.

13. The method according to claim 8, characterized in that In response to the HTTP menu request, menu data is obtained from a database, and the menu data is used as feedback data of the HTTP menu request, including: In response to the first HTTP menu request sent by the browser after logging into the management system, the first HTTP menu request sent after logging into the management system includes an identifier of a menu data branch; The data of the menu data branch corresponding to the identifier is used as feedback data of the HTTP menu request.

14. A data processing device for a management system, characterized in that: include: A reading unit, used by the browser to read target status information in the data warehouse; The first processing unit is used for, when the target state information is not in a predetermined state, the browser calls the back-end interface in the data warehouse to send an HTTP menu request to the server; the HTTP menu request is used to enable the server to obtain menu data from the database, and use the menu data as feedback data of the HTTP menu request; the browser calls the back-end interface in the data warehouse to store the menu data fed back by the server in the browser's cache, and calls the back-end interface in the data warehouse to modify the target state information in the data warehouse to a predetermined state; A second processing unit is used for, when the target state information is a predetermined state, for the browser to call the front-end interface in the data warehouse in real time to obtain the menu data in the cache, and to render a real-time display page of the management system based on the menu data; A first receiving unit, configured to receive a change notification sent by the server; the change notification is sent to the browser in response to a change in menu data in the database; a sending unit, configured to, in response to the change notification, call a backend interface in the data warehouse to send an HTTP menu request to a server to request menu data; The modification unit is used to call the back-end interface in the data warehouse to modify the menu data stored in the browser cache according to the feedback data of the HTTP menu request.

15. A data processing device for a management system, characterized in that: include: A third receiving unit, configured to receive an HTTP menu request sent by a user client, wherein the HTTP menu request is used to obtain menu data; A feedback unit, configured to obtain menu data from a database in response to the HTTP menu request, and use the menu data as feedback data of the HTTP menu request; A monitoring unit, used to monitor data changes in the database; A determination unit, used to determine the target user identifier involved in the data change when data change occurs in the database; The notification unit is used to send a change notification to the browser logged in by the target user identification in the login state; the change notification is used to make the target user client send an HTTP menu request for requesting menu data.

16. An electronic device, characterized in that: include: A memory and a processor, wherein the processor and the memory are communicatively connected to each other, the memory stores computer instructions, and the processor implements the data processing method of the management system according to any one of claims 1 to 13 by executing the computer instructions.

17. A computer storage medium, characterized in that: The computer storage medium stores computer program instructions, and when the computer program instructions are executed, the steps of the data processing method of the management system according to any one of claims 1 to 13 are implemented.

18. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the steps of the data processing method of the management system according to any one of claims 1 to 13.

Images