List rendering method and device, equipment and medium
By categorizing and processing business requests based on importance and response times, the method enhances list rendering efficiency, prioritizing critical data and using lazy loading for non-critical data, addressing the slow rendering of large lists in web applications.
Patent Information
- Application Number
- CN202411831068.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-12
- Publication Date
- 2025-03-18
AI Technical Summary
In web front-end development, rendering large lists of data can be slow due to high interface data volumes and varying efficiency of dependent backend services, leading to prolonged wait times for users and a negative user experience.
A method that categorizes business requests into primary and secondary requests based on importance and historical response times, allowing for separate processing through different business interfaces and services, optimizing data loading by prioritizing critical data and using lazy loading for non-critical data.
This approach reduces the time required to render lists by prioritizing and processing critical data first, improving user experience and reducing server load, while ensuring that users can access essential list data quickly and efficiently.
Smart Images

Figure CN119646340A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to the field of financial technology, and in particular, to a list rendering method, device, equipment and medium. Background Art
[0002] Lists are commonly used components in web front-end development. They are usually used in scenarios where a large number of data items need to be displayed. Browsers often obtain dozens of data at a time and present them to users in the form of a scrolling list.
[0003] When the browser renders the list, it often takes too long to render the list because the amount of interface data is too large, the backend interface indirectly relies on too many services, and the efficiency of the dependent services is uneven. Users need to wait for a long time to see the data in the list, which affects the user experience. Therefore, it is very important to improve the efficiency of list rendering. Summary of the invention
[0004] The present invention provides a list rendering method, device, equipment and medium to improve list rendering efficiency.
[0005] According to one aspect of the present invention, a list rendering method is provided, which is applied to a front-end page, and the method includes:
[0006] Obtain a preset target business item list from the business background, and classify the current business request according to the target business item list to obtain important sub-requests and secondary sub-requests; wherein the target business item list is determined according to the initial business item list, basic sub-item type and historical response time;
[0007] Determine an important data basic list according to the important sub-request, the important business interface of the business background and the important service set, and obtain a basic display page according to the important data basic list;
[0008] According to the secondary sub-request, the secondary business interface of the business background and the secondary service set, a secondary data basic list is determined, and according to the secondary data basic list and the important data value assignment list, a target display page is obtained.
[0009] According to another aspect of the present invention, a list rendering device is provided, which is configured on a front-end page, and the device includes:
[0010] A request classification module is used to obtain a preset target business item list from the business background, and classify the current business request according to the target business item list to obtain important sub-requests and secondary sub-requests; wherein the target business item list is determined according to the initial business item list, basic sub-item type and historical response time;
[0011] A basic display page determination module, used to determine an important data basic list according to the important sub-request, the important business interface and the important service set of the business background, and obtain a basic display page according to the important data basic list;
[0012] The target display page determination module is used to determine the secondary data basic list according to the secondary sub-request, the secondary business interface and the secondary service set of the business background, and obtain the target display page according to the secondary data basic list and the important data assignment list.
[0013] According to another aspect of the present invention, there is provided an electronic device, comprising:
[0014] one or more processors;
[0015] A memory for storing one or more programs;
[0016] When one or more programs are executed by one or more processors, the one or more processors can execute any one of the list rendering methods provided by the embodiments of the present invention.
[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement any one of the list rendering methods provided by the embodiments of the present invention when executed.
[0018] An embodiment of the present invention provides a list rendering solution, which obtains a preset target business project list from a business background, and classifies the current business request according to the target business project list to obtain important sub-requests and secondary sub-requests; wherein the target business project list is determined according to the initial business project list, basic sub-item types and historical response durations; an important data basic list is determined according to the important sub-requests, the important business interfaces of the business background and the important service set, and a basic display page is obtained according to the important data basic list; a secondary data basic list is determined according to the secondary sub-requests, the secondary business interfaces of the business background and the secondary service set, and a target display page is obtained according to the secondary data basic list and the important data basic list. The above scheme divides the sub-requests in the current business request into important sub-requests and secondary sub-requests according to the target business item list, processes the important sub-requests through the important business interface and the important service set, obtains the important data basic list, obtains the basic display page according to the important data basic list, and then processes the secondary sub-requests through the secondary business interface and the secondary service set to obtain the secondary data basic list, obtains the target display page through the secondary data basic list and the important data basic list, thereby realizing the diversion of the sub-requests in the current business request, and processes the sub-requests in the current business request through different business interfaces. The request is processed, thereby improving the response efficiency of the current business request; at the same time, by dividing the current business request into important sub-requests and secondary sub-requests according to the target business project list, the important sub-requests are processed through the important business interface and the important service set, and the secondary sub-requests are processed through the secondary business interface and the secondary service set, thereby realizing the diversion of the current business request according to the importance of the sub-request, improving the timeliness and efficiency of responding to the important sub-requests, avoiding the situation where it takes a long time and is a heavy burden to respond to each sub-request in the current business request at the same time, and improving the user experience.
[0019] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0021] Figure 1 is a flowchart of a list rendering method provided by Embodiment 1 of the present invention;
[0022] Figure 2 is a flowchart of a list rendering method provided by Embodiment 2 of the present invention;
[0023] Figure 3A This is a schematic diagram of a web list rendering dependency service bucket effect provided by Embodiment 3 of the present invention;
[0024] Figure 3B This is a schematic diagram of the efficiency of a web list rendering dependency service bucket provided by the third embodiment of the present invention;
[0025] Figure 3C This is a schematic diagram of batch request provided by Embodiment 3 of the present invention;
[0026] Figure 4 is a structural diagram of a list rendering device provided by Embodiment 4 of the present invention;
[0027] Figure 5 It is a structural diagram of an electronic device for implementing a list rendering method provided in Embodiment 5 of the present invention. DETAILED DESCRIPTION
[0028] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.
[0029] Lazy loading: Lazy loading is also called delayed loading. In the embodiment of the present invention, it refers to the delayed loading of secondary data in a long list in a web page, and the data is loaded on demand only after the module enters the browser viewport.
[0030] Batch requests: In this article, batching HTTP (HyperText Transfer Protocol) requests means changing the data originally returned by a business interface to split interface requests according to priority, so as to avoid unimportant slow interfaces affecting the overall rendering performance of the page.
[0031] Embodiment 1
[0032] Figure 1 It is a flowchart of a list rendering method provided in the first embodiment of the present invention. This embodiment can be applied to the situation of rendering and displaying list data. The method can be executed by a list rendering device, which can be implemented in software and / or hardware and can be configured in an electronic device that carries the list data rendering function.
[0033] See also Figure 1 The list rendering method shown is applied to the front-end page, including:
[0034] S110 , obtaining a preset target business project list from the business background, and classifying the current business request according to the target business project list to obtain important sub-requests and secondary sub-requests.
[0035] The front-end page refers to the web (World Wide Web) front-end page, which can be used to display the page obtained after the list is rendered to the user. The business backend refers to the business backend service, which can be used to process the business request and the data corresponding to the business request. The service collection can be used to provide business data information.
[0036] Exemplarily, the front-end page is connected to the business backend through communication, and the business backend is connected to the service set through communication. For example, the front-end page sends a business request to the business backend, which then forwards the business request to the service set. The service set responds to the business request and feeds back corresponding business data information to the business backend, which then feeds back the business data information to the front-end page, which then renders and displays the business data information.
[0037] Among them, the target business project list refers to a classification table stored in the business background, which is used to record the importance of each business sub-item under the different business types that the business background is responsible for. That is, in the target business project list, the business sub-items under a certain business type that the business background is responsible for are classified according to importance to obtain each business sub-item under importance and each business sub-item under secondary importance.
[0038] Exemplarily, the target business project list is determined based on the initial business project list, basic sub-item type and historical response time. The initial business project list refers to a table of business sub-items involved in the aforementioned business type pre-set by the business backend according to the business type it is responsible for. Business sub-items refer to projects associated with a business type that the business backend is responsible for.
[0039] For example, if the business type A that the business backend is responsible for is online shopping, the initial business item list is the product list, and the business sub-items in the initial business item list may include product price information, product image information, product sales information, product activity information, product sales quantity and product shipping location information, etc.; the important business sub-items in the target business item list may include product price information, product image information and product activity information, etc., and the secondary business sub-items in the target business item list may include product sales information, product sales quantity and product shipping location information, etc.
[0040] Among them, the basic sub-item type refers to the default importance type of each business sub-item in the initial business project list. Exemplarily, the basic sub-item type may include basic important sub-items and basic secondary sub-items. Basic important sub-items refer to the default business sub-items that are important under the corresponding business type that the business background is responsible for. Basic secondary sub-items refer to the default business sub-items that are secondary under the corresponding business type that the business background is responsible for. It should be noted that the basic sub-item type can be set by technical personnel based on experience or needs, and the embodiments of the present invention do not impose any limitations on this. One business sub-item corresponds to one basic sub-item type.
[0041] The historical response duration refers to the response duration of the historical sub-item request corresponding to each business sub-item in the initial business item list in the service set. The historical sub-item request refers to the business request corresponding to the business sub-item at the historical moment.
[0042] Among them, the current business request can be used to indicate the request for business data display on the front-end page at the current moment. The important sub-request refers to the key sub-request in the current business request. The secondary sub-request refers to the secondary sub-request in the current business request. One sub-request corresponds to one business sub-item, and the current business request includes multiple sub-requests.
[0043] Exemplarily, the target business project list records important sub-projects and minor sub-projects. According to the target business project list, the sub-requests corresponding to the important business sub-projects in the current business request are treated as important sub-requests, and the sub-requests corresponding to the minor business sub-projects in the current business request are treated as minor sub-requests.
[0044] Specifically, the front-end page obtains a target business project list from the business backend; the front-end page classifies the sub-requests in the current business request according to the target business project list to obtain important sub-requests and secondary sub-requests.
[0045] S120: Determine an important data basic list according to important sub-requests, important business interfaces of the business background, and important service sets, and obtain a basic display page according to the important data basic list.
[0046] Among them, the important business interface refers to the business interface used to process important sub-requests. The important service set refers to the set of important dependent services used to provide corresponding business data information for important sub-requests. The important service set includes multiple important dependent services. The important dependent service can respond to the important sub-request and determine the corresponding important business data information. Exemplarily, one important dependent service can correspond to one important business sub-item, that is, one important dependent service can correspond to one important sub-request.
[0047] The important data basic list refers to a data list composed of business data information corresponding to important sub-requests. The basic display page refers to a page that only displays important business data information.
[0048] In an optional embodiment, a basic list of important data is determined based on important sub-requests, important business interfaces of the business background, and important service sets, and a basic display page is obtained based on the basic list of important data, including: sending the important sub-requests to the corresponding important service sets through the important business interfaces of the business background, and receiving the basic list of important data fed back by the important service sets through the important business interfaces; assigning important sub-items of each display item in the basic list of important data to obtain an important data assignment list, and rendering the important data assignment list to obtain a basic display page.
[0049] Among them, display items refer to the total items displayed on the page. Important sub-items refer to important business sub-items, that is, business sub-items displayed on the basic display page. For example, if the business backend is responsible for online shopping, the display items may include product A and product B. The important sub-items of product A may include product price information, product image information, product activity information, etc.; similarly, the important sub-items of product B may include product price information, product image information, product activity information, etc.
[0050] The important data assignment list refers to a list obtained by assigning the data of important sub-items in the important data basic list to displayable variables.
[0051] Exemplarily, the front-end page immediately sends the important sub-request to the important business interface of the business background; the important business interface forwards the important sub-request to the corresponding important dependent service in the important service set; the important dependent service responds to the important sub-request and sends the corresponding important data (i.e., important business data) to the important business interface; the important business interface processes the important data to obtain a basic list of important data; the important business interface sends the basic list of important data to the front-end page; the front-end page assigns the important data in the basic list of important data to observable variables of Vue to obtain an important data assignment list; the front-end page traverses and renders the data in the important data assignment list to obtain an important data rendering document; the front-end page obtains a basic display page based on the important data rendering document. The important data rendering document refers to a document obtained by rendering the important data assignment list.
[0052] It can be understood that by sending important sub-requests to the important service set through the important business interface, and receiving the important data basic list fed back by the important service set through the important business interface, it is possible to separately process the important sub-requests through the important business interface, thereby reducing the request response time and improving the request response efficiency; at the same time, by assigning and rendering the important data basic list, the basic display page is obtained, which makes it possible to first process the important sub-requests in the current business request, and then render and display the processing results, thereby improving the user experience.
[0053] Specifically, the front-end page sends the important sub-request to the important service set through the important business interface of the business background, and receives the important data basic list fed back by the important service set through the important business interface; the front-end page assigns and renders the important data basic list, obtains the basic display page and displays it.
[0054] S130, determining a secondary data basic list according to the secondary sub-request, the secondary business interface of the business background and the secondary service set, and obtaining a target display page according to the secondary data basic list and the important data basic list.
[0055] Among them, the secondary business interface refers to the business interface used to process the secondary sub-request. The secondary service set refers to the set of secondary dependent services used to provide corresponding business data information for the secondary sub-request. The secondary service set includes multiple secondary dependent services. The secondary dependent service can determine the corresponding secondary business data information in response to the secondary sub-request. Exemplarily, one secondary dependent service can correspond to one secondary business sub-item, that is, one secondary dependent service can correspond to one secondary sub-request.
[0056] The secondary data base list refers to a data list composed of business data information corresponding to the secondary sub-requests. The target display page refers to a page that displays all (including important and secondary) business data information.
[0057] In an optional embodiment, a secondary data basic list is determined according to a secondary sub-request, a secondary business interface of a business background, and a secondary service set, and a target display page is obtained according to the secondary data basic list and the important data basic list, including: based on preset secondary data display conditions, sending the secondary sub-request to a corresponding secondary service set through the secondary business interface of the business background, and receiving the secondary data basic list fed back by the secondary service set through the secondary business interface; assigning values to secondary sub-items of each display item in the secondary data basic list to obtain a secondary data assignment list, and based on the secondary data assignment list, updating the important data assignment list to obtain a page display data list; rendering the page display data list to obtain a target display page.
[0058] Among them, the preset secondary data display condition refers to the pre-set condition for displaying secondary data. In an optional embodiment, the preset secondary data display condition is that the basic display page has been displayed, or the display item boundary in the important data assignment list intersects with the front-end display area boundary. Among them, the front-end display area is the browser viewport, which refers to the area that the user can see. For example, if a product list is very long with a total of 100 products, the user can only see the first 5 products in the browser, and the other 95 products are outside the viewport and need to drop down the list to see them. At this time, the front-end display area boundary has been reached.
[0059] Exemplarily, after the basic display page has been displayed, the front-end page starts sending secondary sub-requests to the secondary business interface; or, when the display item boundary in the important data assignment list intersects with the front-end display area boundary, the front-end page starts sending secondary sub-requests to the secondary business interface.
[0060] It can be understood that by intersecting the boundaries of the display items in the displayed basic display page and the front-end display area boundaries in the important data assignment list, the preset secondary data display conditions are determined, which improves the richness of the preset secondary data display conditions and improves the timeliness of subsequent secondary sub-request responses.
[0061] Among them, secondary sub-items refer to secondary business sub-items, that is, business sub-items used to supplement the important sub-items in the basic display page. For example, if the business backend is responsible for online shopping, the display items may include product A and product B. The important sub-items of product A may include product sales information, product sales quantity and product shipping location information; similarly, the important sub-items of product B may include product sales information, product sales quantity and product shipping location information.
[0062] Among them, the secondary data assignment list refers to the list obtained by assigning the data of the secondary sub-items in the secondary data basic list to displayable variables. The page display data list refers to the data list obtained by updating the important data assignment list according to the secondary data assignment list.
[0063] Exemplarily, the front-end page sends the secondary sub-request to the secondary business interface of the business background through lazy loading; the secondary business interface forwards the secondary sub-request to the corresponding secondary dependent service in the secondary service set; the secondary dependent service responds to the secondary sub-request and sends the corresponding secondary data (i.e., secondary business data) to the secondary business interface; the secondary business interface processes the secondary data to obtain a secondary data basic list; the secondary business interface sends the secondary data basic list to the front-end page; the front-end page assigns the secondary data in the secondary data basic list to the observable variables of Vue to obtain a secondary data assignment list; the front-end page updates the important data assignment list according to the secondary data assignment list to obtain a page display data list; the front-end page traverses and renders the data in the page display data list to obtain a page data rendering document; the front-end page obtains the target display page according to the page data rendering document. The page data rendering document refers to the document obtained by rendering the page display data list.
[0064] It should be noted that during the second rendering, the rendered data will not be rendered repeatedly, but the business data corresponding to the secondary sub-items will be rendered.
[0065] It can be understood that by sending the secondary sub-request to the secondary service set through the secondary business interface, and receiving the secondary data basic list fed back by the secondary service set through the secondary business interface, the separate processing of the secondary sub-request through the secondary business interface is achieved, thereby improving the response efficiency of the request; at the same time, through the secondary data assignment list, the important data assignment list is updated to obtain the page display data list, and the page display data list is rendered to obtain the target display page, thereby achieving the supplement of the data in the target display page and improving the comprehensiveness of the information in the target display page.
[0066] Exemplarily, the front-end page sends the secondary sub-request to the secondary service set through the secondary business interface of the business background, and receives the secondary data basic list fed back by the secondary service set through the secondary business interface; the front-end page performs assignment processing on the secondary data basic list to obtain the secondary data assignment list; the front-end page updates the important data assignment list according to the secondary data assignment list, and renders the updated important data assignment list (i.e., the page display data list) to obtain the target display page.
[0067] The important dependent services in the important service set in the embodiment of the present invention can be determined based on the important sub-items in the target business item list. Similarly, the secondary dependent services in the secondary service set can be determined based on the secondary sub-items in the target business item list.
[0068] An embodiment of the present invention provides a list rendering solution, which obtains a preset target business project list from a business background, and classifies the current business request according to the target business project list to obtain important sub-requests and secondary sub-requests; wherein the target business project list is determined according to the initial business project list, basic sub-item types and historical response durations; an important data basic list is determined according to the important sub-requests, the important business interfaces of the business background and the important service set, and a basic display page is obtained according to the important data basic list; a secondary data basic list is determined according to the secondary sub-requests, the secondary business interfaces of the business background and the secondary service set, and a target display page is obtained according to the secondary data basic list and the important data basic list. The above scheme divides the sub-requests in the current business request into important sub-requests and secondary sub-requests according to the target business item list, processes the important sub-requests through the important business interface and the important service set, obtains the important data basic list, obtains the basic display page according to the important data basic list, and then processes the secondary sub-requests through the secondary business interface and the secondary service set to obtain the secondary data basic list, obtains the target display page through the secondary data basic list and the important data basic list, thereby realizing the diversion of the sub-requests in the current business request, and processes the sub-requests in the current business request through different business interfaces. The request is processed, thereby improving the response efficiency of the current business request; at the same time, by dividing the current business request into important sub-requests and secondary sub-requests according to the target business project list, the important sub-requests are processed through the important business interface and the important service set, and the secondary sub-requests are processed through the secondary business interface and the secondary service set, thereby realizing the diversion of the current business request according to the importance of the sub-request, improving the timeliness and efficiency of responding to the important sub-requests, avoiding the situation where it takes a long time and is a heavy burden to respond to each sub-request in the current business request at the same time, and improving the user experience.
[0069] Embodiment 2
[0070] Figure 2 It is a flowchart of a list rendering method provided by the second embodiment of the present invention. Based on the above embodiments, this embodiment further adds the operations of "determining the basic sub-item type of each business sub-item in the initial business item list according to the business type corresponding to the initial business item list; determining the historical response time of the historical sub-item request corresponding to each business sub-item in the initial business item list in the service set; determining the target sub-item type of the business sub-item according to the basic sub-item type and / or the historical response time; generating a target business item list according to the business sub-item and the corresponding target sub-item type" to improve the determination mechanism of the target business item list. It should be noted that for the parts not described in detail in the embodiments of the present invention, reference may be made to the descriptions of other embodiments.
[0071] See also Figure 2 The list rendering method shown includes:
[0072] S210: Determine the basic sub-item type of each business sub-item in the initial business item list according to the business type corresponding to the initial business item list.
[0073] Among them, the business type refers to the business type corresponding to the initial business item list. For example, the business type can be online shopping. The basic sub-item type refers to the default importance type of each business sub-item in the initial business item list. Exemplarily, the basic sub-item type may include basic important sub-items and basic secondary sub-items. Basic important sub-items refer to the default business sub-items that are important under the corresponding business type that the business background is responsible for. Basic secondary sub-items refer to the default business sub-items that are secondary under the corresponding business type that the business background is responsible for.
[0074] Specifically, the business backend determines the basic sub-item type of each business sub-item in the initial business item list according to the business type corresponding to the initial business item list.
[0075] S220: Determine the historical response time of the historical sub-item request corresponding to each business sub-item in the initial business item list in the service set.
[0076] The historical sub-item request refers to the business request corresponding to the business sub-item at the historical moment. The historical response duration refers to the response duration of the historical sub-item request corresponding to each business sub-item in the initial business item list in the service set.
[0077] Specifically, the business backend may obtain the historical response time of the historical sub-item requests corresponding to each business sub-item in the initial business item list in the service set.
[0078] S230: Determine the target sub-item type of the business sub-item according to the basic sub-item type and / or the historical response time.
[0079] Among them, the target sub-item type refers to the importance type of the business sub-item determined based on the basic sub-item type and / or the historical response time. The target sub-item type can include target important sub-items and target secondary sub-items. The target important sub-item means that in actual applications, the business sub-item is important under the corresponding business type that the business backend is responsible for. The target secondary sub-item means that in actual applications, the business sub-item is secondary under the corresponding business type that the business backend is responsible for.
[0080] In an optional embodiment, the target sub-item type of the business sub-item is determined based on the historical response time, including: if the historical response time of the business sub-item is greater than a preset response time threshold, then the target sub-item type of the business sub-item is determined to be a target secondary sub-item; if the historical response time of the business sub-item is less than or equal to the preset response time threshold, then the target sub-item type of the business sub-item is determined to be a target important sub-item.
[0081] The embodiment of the present invention does not impose any limitation on the size of the preset response time threshold, which can be set by a technician based on experience or needs, or determined repeatedly through a large number of experiments.
[0082] Exemplarily, for any business sub-item, if the historical response time of the business sub-item is greater than the preset response time threshold, the target sub-item type of the business sub-item is determined to be a target secondary sub-item; if the historical response time of the business sub-item is less than or equal to the preset response time threshold, the target sub-item type of the business sub-item is determined to be a target important sub-item.
[0083] It can be understood that by introducing a preset response time threshold, the target sub-item type of the business sub-item is determined according to the historical response time and the preset response time threshold, thereby improving the accuracy of the determined target sub-item type.
[0084] It should be noted that, for any business sub-item, if the basic sub-item type of the business sub-item is a basic important sub-item, and the historical response time of the business sub-item is less than or equal to the preset response time threshold, then the target sub-item type of the business sub-item is determined to be a target important sub-item; if the basic sub-item type of the business sub-item is a basic important sub-item, and the historical response time of the business sub-item is greater than the preset response time threshold, then the basic sub-item type of the business sub-item is re-determined, and then the target sub-item type of the business sub-item is re-determined, or the target sub-item type of the business sub-item is directly determined. is a target important sub-item; if the basic sub-item type of the business sub-item is a basic secondary sub-item, and the historical response time of the business sub-item is less than or equal to the preset response time threshold, the basic sub-item type of the business sub-item is re-determined, and then the target sub-item type of the business sub-item is re-determined, or the target sub-item type of the business sub-item is directly determined as a target important sub-item; if the basic sub-item type of the business sub-item is a basic secondary sub-item, and the historical response time of the business sub-item is greater than the preset response time threshold, then the target sub-item type of the business sub-item is determined to be a target secondary sub-item.
[0085] Specifically, the background business may determine the target sub-item type of the business sub-item according to the basic sub-item type and / or the historical response time.
[0086] S240: Generate a target business item list according to the business sub-items and corresponding target sub-item types.
[0087] Specifically, the business backend can classify each business sub-item according to the target sub-item type corresponding to each business sub-item to obtain important sub-items and minor sub-items, and generate a target business project list including important sub-items and minor sub-items. Among them, the important sub-item can be the business sub-item corresponding to the target important sub-item; the minor sub-item can be the business sub-item corresponding to the target minor sub-item.
[0088] S250: Obtain a preset target business project list from the business background, and classify the current business request according to the target business project list to obtain important sub-requests and secondary sub-requests.
[0089] The target business item list is determined based on the initial business item list, basic sub-item types and historical response times.
[0090] S260: Determine an important data basic list according to important sub-requests, important business interfaces of the business background, and important service sets, and obtain a basic display page according to the important data basic list.
[0091] S270: Determine a secondary data base list according to the secondary sub-request, the secondary business interface of the business background, and the secondary service set, and obtain a target display page according to the secondary data base list and the important data value assignment list.
[0092] The embodiment of the present invention provides a list rendering scheme, which determines the basic sub-item type of each business sub-item in the initial business item list by adding the business type corresponding to the initial business item list; determines the historical response time of the historical sub-item request corresponding to each business sub-item in the initial business item list in the service set; determines the target sub-item type of the business sub-item according to the basic sub-item type and / or the historical response time; generates a target business item list operation according to the business sub-item and the corresponding target sub-item type, thereby improving the determination mechanism of the target business item list. The above scheme improves the accuracy of the generated target business item list by determining the target sub-item type of the business sub-item according to the basic sub-item type and the historical response time, and then generating the target business item list according to the business sub-item and the corresponding target sub-item type.
[0093] Embodiment 3
[0094] The embodiment of the present invention provides an optional example based on the above embodiment. It should be noted that for the part not described in detail in the embodiment of the present invention, reference can be made to the description of other embodiments.
[0095] In the case of a weak network, the existing list rendering method cannot see the data in the list due to the long loading time of the list data. This may even cause the loss of users and indirectly lead to the loss of website assets. Common methods for optimizing list data loading include increasing network speed and compressing the data returned by the interface. These methods have certain limitations. For example, network conditions may be limited by different regions and operators. Compressing the data returned by the interface also has certain limits and cannot solve the bucket effect of the backend relying on many services. That is, the interface can only respond to the front end after the slowest service returns.
[0096] For example, see Figure 3A The web list rendering dependency service bucket effect diagram is shown. The web front-end page requests list data from the business back-end service through the interface, and the service back-end obtains data from many dependent services (such as dependent service 1, dependent service 2...dependent service n) at the same time. Since the back-end dependent service n takes at least 300ms to respond, the business back-end service data is ready (preparation) time is 300ms, and then the summary data is responded to the web front-end page. The time from the web front-end page to the business back-end request and response is 400ms, so the total time is 300ms+400ms=700ms.
[0097] For example, the current common method to solve the bucket effect is to concurrently request many dependent services on the web front end. Each time a dependent service returns data, the data is immediately rendered to the page. In this way, independent requests between dependent services do not need to wait until all dependencies are loaded before rendering the page. The service interface that responds first is rendered first, and the service interface that responds later is rendered later. This method does not directly rely on the business backend service to unify the request and aggregate data, which can effectively solve the efficiency of the dependent service bucket. The fastest responding interface is also rendered to the page in time, and the front-end page first screen time will be effectively reduced. Users can see part of the page content faster, and then see the rest of the page content in sequence. In addition, this solution eliminates the time-consuming intermediate link of the business backend service, further reduces the response speed of the interface, and indirectly improves the performance of the first screen (i.e., the basic display page) of the page.
[0098] For example, see Figure 3B The diagram shows the bucket efficiency of web list rendering dependency services. Directly requesting dependency services from the web front-end page will result in a slower interface response than requesting dependency services through the business backend service because the web user is on the external network. However, without the middle layer of the business backend service, and without the bucket efficiency of each interface request, the overall page rendering speed will be greatly improved.
[0099] The existing technology has the following disadvantages: due to the limitation on the number of concurrent requests under the same domain name of the browser (usually 6-8), if the limit is exceeded, the data interface becomes serial, and the existing technical solution is not suitable for large websites that rely on many services, nor is it suitable for adding more interfaces during subsequent website expansion and construction; after each service interface returns data, the data is immediately rendered on the page, and page update rendering is a DOM (Document Object Model) reflux and redrawing process with large performance consumption, and too frequent rendering will cause page freezes or even page crashes; the web front-end page directly requests the back-end interface, and the business back-end service cannot centrally process login, fault-tolerant processing, and log collection; the web front-end page makes concurrent requests to dependent services, and the interface data response priority is only related to the response time. There is no priority and no focus, which usually cannot meet the actual business needs of giving priority to rendering key modules.
[0100] The purpose of the list rendering scheme provided by the embodiment of the present invention is to optimize the front-end list rendering performance based on lazy loading and batch requests, by determining the priority of the request according to the business sub-items in the initial business project list items at the business level (i.e., the basic sub-item type) and the response time of the dependent service (i.e., the historical response time), and dividing the service into important business data interfaces and secondary business data interfaces, and then only requesting the important business data interface on the first screen, and delaying the request in the form of lazy loading for the secondary business data interface, thereby improving the speed of the web front-end page rendering list and reducing the server pressure. At the same time, by adopting the embodiment of the present invention, users of the web front-end page can quickly see the business data corresponding to the important sub-items in the target business project list, and then delay seeing the business data corresponding to the secondary sub-items, which improves the user experience, improves the competitiveness of the website, and indirectly increases the company's economic benefits.
[0101] For example, in the port list of online shopping (i.e., the initial business project list), the list item is one of the products in the port list, which displays the information of the current product, such as product image, product name, model, price, number of people who have purchased, and product evaluation information; the importance is determined by the developer according to the business, such as the price, product image, product name, and model of the product that must be determined when placing an order is important information, i.e., important sub-items, while the number of people who have purchased, etc., which do not affect the user's order, is secondary information, i.e., secondary sub-items; the response time of the dependent service is determined by the actual measurement of the interface request. If there are two interfaces in total, the total time from request to response of the two interfaces is calculated through the front-end tracking point, that is, when the request is sent, a time a is recorded, and when the request receives the result, a time b is recorded, and ba is the response time of this request; the important sub-items and secondary sub-items in the target business project list are divided based on the importance of the interface information and the response time (i.e., the historical response time). For example, the business data of the business sub-items of the basic important sub-items and the secondary interface data with a historical response time within 3s are the first screen requests, and the secondary business interface data with a response time of more than 3s are the second screen requests.
[0102] For example, see Figure 3C The batch request diagram is shown in the figure. The business backend provides both important business interfaces and secondary business interfaces. When the important business interface relies on the web front-end page to render the list data, it immediately requests the important and indispensable data in the list items (i.e., important sub-requests) from the important business interface in the business backend service, such as the description information (desc) of the goods in the online shopping goods list, the link of the goods image (imageURL), and the price (price) of the goods. The important business interface obtains business data from the corresponding important dependent services respectively, and summarizes the response to the web front-end page for rendering the front-end page, that is, sending the important data basic list to the front-end page, and the front-end page renders the important data basic list to obtain the basic display page. After the browser front-end page obtains the first screen data (i.e., the important data basic list), it assigns the data in the important data basic list to the observable variable of Vue, and then traverses the array rendering list DOM and obtains related images and other resources.
[0103] Continuing with the above example, after obtaining the list of important data values, the list is traversed and rendered, and the data is filled into the web page. For example, important sub-items include port description (desc) and port price (price), and the product image resources are obtained according to the imageURL (database image splicing) to display to the user. After the list renders these important data, the user can browse the list normally and trade normally. It is a port list with specific basic functions. The user can obtain the key information of the product in the current list and conduct normal product transactions.
[0104] For example, listen to the page onload event (that is, the event that is automatically triggered after the browser parses the page) and bind the event or add IntersectionObserver to the list item (used to monitor the intersection status between the target element and its ancestor element, that is, whether it enters or leaves the viewport). The former is triggered after the page has been loaded, that is, the basic display page has been displayed; the latter is triggered when the list item enters the browser viewport (that is, the list item boundary intersects with the browser viewport boundary), that is, the display item boundary in the important data assignment list intersects with the front-end display area boundary. When the event is triggered, the secondary business of calling the business background service is triggered. The interface obtains the secondary data corresponding to the secondary business. The business background requests the secondary data from the secondary dependent services respectively and summarizes the responses to the front-end web page, that is, the basic list of secondary data is fed back to the front-end page; when requesting the secondary business interface, the page already has basic functions, so even if the response speed and efficiency of the secondary data interface are slow under the bucket effect, it will not affect the normal use of the website; after the front-end web page obtains the secondary data of the secondary business interface, it can traverse the corresponding items assigned to the list array through a for loop. Since the data in the important data assignment list has been assigned to observable variables, assigning the data in the secondary data basic list at this time will trigger the page list to be re-rendered. According to the characteristics of the Vue diff algorithm, since the important data of the important business interface has not changed, the page elements corresponding to the important business interface will not be rendered repeatedly, and the secondary data will be incrementally rendered to the basic display page, that is, rendering the complete business sub-items will not cause large-scale DOM reflux.
[0105] Continuing with the previous example, the secondary business interface obtains the shipping location and sales volume information and assigns them to the secondary data basic list to obtain the secondary data assignment list, triggering the view update, which is rendered to each display item on the interface to fully display the display item data.
[0106] The embodiment of the present invention provides a list rendering solution, in which the important data interface of the first screen only provides a small amount of important and indispensable data in the list items (i.e., display items). Therefore, the data volume of the important business interface of the first screen is small, the transmission speed is high, and the first screen rendering speed of the page list is improved; the important business interface of the first screen does not load secondary data, which saves the server performance and bandwidth consumption of the important business interface of the first screen, and indirectly reduces the first screen rendering time of the list; the back-end interface is loaded according to priority, and the front-end lazily loads the secondary data, does not block the loading of other resources of the page and the running of scripts, and improves the performance of the page; batch loading is relative to each list item separately requested, which reduces the number of concurrent browser requests, avoids mutual blocking of http requests, improves the list rendering efficiency, and at the same time reduces the number of requests, reducing the pressure on the secondary data server; the number of browser request interfaces is small, which avoids mutual blocking of interfaces and other resources, and improves the browser network request efficiency; lazy loading of secondary data can reduce the pressure on secondary dependent servers, which not only reduces the risk of server crashes and indirectly saves research and development costs, but also reduces the rendering frequency of the browser and improves page performance.
[0107] The embodiment of the present invention can be implemented in a web front-end page, and can also be implemented in other terminals with an operating system.
[0108] It should be noted that the information collected in the embodiments of the present invention is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse; if the user chooses to refuse, the expert decision-making process will be entered.
[0109] Embodiment 4
[0110] Figure 4 1 is a schematic diagram of the structure of a list rendering device provided in Embodiment 4 of the present invention. This embodiment is applicable to the case of rendering and displaying list data, and the method can be executed by a list rendering device, which can be implemented in software and / or hardware, and can be configured in an electronic device that carries the list data rendering function.
[0111] like Figure 4 As shown, the device is configured on the front-end page, and includes: a request classification module 310, a basic display page determination module 320 and a target display page determination module 330.
[0112] The request classification module 310 is used to obtain a preset target business item list from the business background, and classify the current business request according to the target business item list to obtain important sub-requests and secondary sub-requests; wherein the target business item list is determined according to the initial business item list, basic sub-item type and historical response time;
[0113] A basic display page determination module 320 is used to determine an important data basic list according to the important sub-request, the important business interface of the business background and the important service set, and obtain a basic display page according to the important data basic list;
[0114] The target display page determination module 330 is used to determine the secondary data basic list according to the secondary sub-request, the secondary business interface and the secondary service set of the business background, and obtain the target display page according to the secondary data basic list and the important data basic list.
[0115] An embodiment of the present invention provides a list rendering solution, which obtains a preset target business project list from a business background, and classifies the current business request according to the target business project list to obtain important sub-requests and secondary sub-requests; wherein the target business project list is determined according to the initial business project list, basic sub-item types and historical response durations; an important data basic list is determined according to the important sub-requests, the important business interfaces of the business background and the important service set, and a basic display page is obtained according to the important data basic list; a secondary data basic list is determined according to the secondary sub-requests, the secondary business interfaces of the business background and the secondary service set, and a target display page is obtained according to the secondary data basic list and the important data basic list. The above scheme divides the sub-requests in the current business request into important sub-requests and secondary sub-requests according to the target business item list, processes the important sub-requests through the important business interface and the important service set, obtains the important data basic list, obtains the basic display page according to the important data basic list, and then processes the secondary sub-requests through the secondary business interface and the secondary service set to obtain the secondary data basic list, obtains the target display page through the secondary data basic list and the important data basic list, thereby realizing the diversion of the sub-requests in the current business request, and processes the sub-requests in the current business request through different business interfaces. The request is processed, thereby improving the response efficiency of the current business request; at the same time, by dividing the current business request into important sub-requests and secondary sub-requests according to the target business project list, the important sub-requests are processed through the important business interface and the important service set, and the secondary sub-requests are processed through the secondary business interface and the secondary service set, thereby realizing the diversion of the current business request according to the importance of the sub-request, improving the timeliness and efficiency of responding to the important sub-requests, avoiding the situation where it takes a long time and is a heavy burden to respond to each sub-request in the current business request at the same time, and improving the user experience.
[0116] Optionally, the target business item list is determined based on the following means:
[0117] A basic sub-item type determination module, used to determine the basic sub-item type of each business sub-item in the initial business item list according to the business type corresponding to the initial business item list;
[0118] A historical response duration determination module, used to determine the historical response duration of the historical sub-item request corresponding to each business sub-item in the initial business item list in the service set;
[0119] A target sub-item type determination module, used to determine the target sub-item type of the business sub-item according to the basic sub-item type and / or the historical response duration;
[0120] The target business item list determination module is used to generate the target business item list according to the business sub-items and corresponding target sub-item types.
[0121] Optionally, a target sub-item type determination module is specifically used to:
[0122] If the historical response time of the business sub-item is greater than the preset response time threshold, determining the target sub-item type of the business sub-item to be a target secondary sub-item;
[0123] If the historical response time of the business sub-item is less than or equal to the preset response time threshold, it is determined that the target sub-item type of the business sub-item is a target important sub-item.
[0124] Optionally, the basic display page determination module 320 includes:
[0125] An important data basic list determining unit, used for sending the important sub-request to a corresponding important service set through an important business interface of a business background, and receiving an important data basic list fed back by the important service set through the important business interface;
[0126] The basic display page determination unit is used to assign values to important sub-items of each display item in the important data basic list to obtain an important data value assignment list, and render the important data value assignment list to obtain a basic display page.
[0127] Optionally, the target display page determination module 330 includes:
[0128] A secondary data basic list determining unit, configured to send the secondary sub-request to a corresponding secondary service set through a secondary service interface of the service background based on a preset secondary data display condition, and receive a secondary data basic list fed back by the secondary service set through the secondary service interface;
[0129] a page display data list determination unit, configured to assign values to the secondary sub-items of each display item in the secondary data basic list to obtain a secondary data value assignment list, and based on the secondary data value assignment list, update the important data value assignment list to obtain a page display data list;
[0130] The target display page determining unit is used to render the page display data list to obtain a target display page.
[0131] Optionally, the preset secondary data display condition is that the basic display page has been displayed, or the display item boundary in the important data value assignment list intersects with the front-end display area boundary.
[0132] The list rendering device provided in the embodiment of the present invention can execute the list rendering method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing each list rendering method.
[0133] In the technical solution of the present invention, the collection, storage, use, processing, transmission, provision and disclosure of current business requests and historical response times, etc., are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0134] According to an embodiment of the present invention, the present invention also provides an electronic device, a readable storage medium and a computer program product.
[0135] Embodiment 5
[0136] Figure 5 It is a structural diagram of an electronic device for implementing a list rendering method provided by Embodiment 5 of the present invention. Electronic device 410 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.
[0137] like Figure 5 As shown, the electronic device 410 includes at least one processor 411, and a memory connected to the at least one processor 411 in communication, such as a read-only memory (ROM) 412, a random access memory (RAM) 413, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 411 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 412 or the computer program loaded from the storage unit 418 to the random access memory (RAM) 413. In the RAM 413, various programs and data required for the operation of the electronic device 410 can also be stored. The processor 411, the ROM 412, and the RAM 413 are connected to each other via a bus 414. An input / output (I / O) interface 415 is also connected to the bus 414.
[0138] Multiple components in the electronic device 410 are connected to the I / O interface 415, including: an input unit 416, such as a keyboard, a mouse, etc.; an output unit 417, such as various types of displays, speakers, etc.; a storage unit 418, such as a disk, an optical disk, etc.; and a communication unit 419, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 419 allows the electronic device 410 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0139] The processor 411 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 411 executes the various methods and processes described above, such as the list rendering method.
[0140] In some embodiments, the list rendering method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 418. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 410 via the ROM 412 and / or the communication unit 419. When the computer program is loaded into the RAM 413 and executed by the processor 411, one or more steps of the list rendering method described above may be performed. Alternatively, in other embodiments, the processor 411 may be configured to perform the list rendering method in any other appropriate manner (e.g., by means of firmware).
[0141] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0142] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0143] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0144] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).
[0145] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0146] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.
[0147] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.
[0148] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. A list rendering method, characterized in that: Applied to the front-end page, the method includes: Obtain a preset target business item list from the business background, and classify the current business request according to the target business item list to obtain important sub-requests and secondary sub-requests; wherein the target business item list is determined according to the initial business item list, basic sub-item type and historical response time; Determine an important data basic list according to the important sub-request, the important business interface of the business background and the important service set, and obtain a basic display page according to the important data basic list; According to the secondary sub-request, the secondary business interface of the business background and the secondary service set, a secondary data basic list is determined, and according to the secondary data basic list and the important data basic list, a target display page is obtained.
2. The method according to claim 1, characterized in that The target business project list is determined based on the following method: Determining a basic sub-item type of each business sub-item in the initial business item list according to the business type corresponding to the initial business item list; Determine the historical response time of the historical sub-item request corresponding to each business sub-item in the initial business item list in the service set; Determining a target sub-item type of the business sub-item according to the basic sub-item type and / or the historical response duration; The target business item list is generated according to the business sub-items and corresponding target sub-item types.
3. The method according to claim 2, characterized in that Determining the target sub-item type of the business sub-item according to the historical response time includes: If the historical response time of the business sub-item is greater than the preset response time threshold, determining the target sub-item type of the business sub-item to be a target secondary sub-item; If the historical response time of the business sub-item is less than or equal to the preset response time threshold, it is determined that the target sub-item type of the business sub-item is a target important sub-item.
4. The method according to claim 1, characterized in that: Determining an important data basic list according to the important sub-request, the important business interface of the business background and the important service set, and obtaining a basic display page according to the important data basic list, includes: Sending the important sub-request to the corresponding important service set through the important business interface of the business background, and receiving the important data base list fed back by the important service set through the important business interface; Assign values to important sub-items of each display item in the important data basic list to obtain an important data value assignment list, and render the important data value assignment list to obtain a basic display page.
5. The method according to claim 4, characterized in that The determining of a secondary data base list according to the secondary sub-request, the secondary business interface of the business background and the secondary service set, and obtaining a target display page according to the secondary data base list and the important data base list, includes: Based on the preset secondary data display condition, the secondary sub-request is sent to the corresponding secondary service set through the secondary service interface of the service background, and the secondary data basic list fed back by the secondary service set through the secondary service interface is received; Assigning values to the secondary sub-items of each display item in the secondary data basic list to obtain a secondary data value assignment list, and updating the important data value assignment list based on the secondary data value assignment list to obtain a page display data list; The page display data list is rendered to obtain a target display page.
6. The method according to claim 5, characterized in that The preset secondary data display condition is that the basic display page has been displayed, or the display item boundary in the important data value assignment list intersects with the front-end display area boundary.
7. A list rendering device, characterized in that: Configured on the front-end page, the device includes: A request classification module is used to obtain a preset target business item list from the business background, and classify the current business request according to the target business item list to obtain important sub-requests and secondary sub-requests; wherein the target business item list is determined according to the initial business item list, basic sub-item type and historical response time; A basic display page determination module, used to determine an important data basic list according to the important sub-request, the important business interface and the important service set of the business background, and obtain a basic display page according to the important data basic list; The target display page determination module is used to determine the secondary data basic list according to the secondary sub-request, the secondary business interface and the secondary service set of the business background, and obtain the target display page according to the secondary data basic list and the important data assignment list.
8. An electronic device, characterized in that: include: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement a list rendering method as described in any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, a list rendering method as described in any one of claims 1 to 6 is implemented.
10. A computer program product, comprising a computer program / instruction, wherein when the computer program / instruction is executed by a processor, the steps of the list rendering method according to any one of claims 1 to 6 are implemented.