Page loading method and system, electronic equipment and computer readable medium

Abstract

The invention discloses a page loading method and system, electronic equipment and a computer readable medium, and the method comprises the steps that after a front end receives page description information which is sent by a client and used for describing a target page, the front end loads the target page according to the page description information, so that the front end can complete a page loading task, and the page loading efficiency is improved. Therefore, the defects existing when the client completes the page loading task can be effectively avoided.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a page loading method, system, electronic device, and computer-readable medium. Background Art

[0002] In some application scenarios, users can not only view certain resource data (such as video data, etc.) on a page, but also implement corresponding interactive processes (such as receiving red envelopes, sharing resources, etc.) by operating certain controls on the page.

[0003] However, how to better implement page loading is a technical problem that needs to be solved urgently. Summary of the invention

[0004] In order to solve the above technical problems, the present application provides a page loading method, system, electronic device, and computer-readable medium.

[0005] In order to achieve the above objectives, the technical solutions provided by this application are as follows:

[0006] The present application provides a page loading method, which is applied to a front end and includes:

[0007] Receiving page description information sent by a client, wherein the page description information is used to describe a target page;

[0008] According to the page description information, the target page is loaded.

[0009] In a possible implementation manner, the page description information includes a page identifier of the target page;

[0010] and / or,

[0011] The page description information is obtained by the client through requesting the server.

[0012] In a possible implementation manner, the method further includes:

[0013] Receiving control description information sent by the client, where the control description information is used to describe a first control;

[0014] According to the control description information, the first control is displayed on the target page.

[0015] In a possible implementation manner, the method further includes:

[0016] If it is determined that the target page has been loaded, a page loading completion prompt message is generated;

[0017] The page loading completion prompt information is sent to the client, and the client is used to display the first control on the target page according to the control description information, and the control description information is used to describe the first control.

[0018] In a possible implementation manner, the control description information includes configuration information of the first control;

[0019] and / or,

[0020] The control description information is obtained by the client through requesting the server.

[0021] In a possible implementation manner, the method further includes:

[0022] When at least one control is displayed on the target page, if a control triggering event corresponding to a second control in the at least one control sent by the client is received, a first operation logic corresponding to the control triggering event is executed.

[0023] In a possible implementation manner, the method further includes:

[0024] If it is determined that the first operation logic is executed completely, a logic request event corresponding to the second control is generated, where the logic request event is used to request the client to execute the second operation logic corresponding to the control trigger event;

[0025] The logic request event is sent to the client, and the client is used to execute the second operation logic.

[0026] The present application provides a page loading method, which is applied to a client and includes:

[0027] Receiving page description information sent by the server, wherein the page description information is used to describe the target page;

[0028] The page description information is sent to a front end, and the front end is used to load the target page according to the page description information.

[0029] In a possible implementation manner, the receiving the page description information sent by the server includes:

[0030] Receiving page description information and control description information sent by the server, wherein the control description information is used to describe a first control;

[0031] The method further comprises:

[0032] After receiving the page loading completion prompt information sent by the front end, the first control is displayed on the target page according to the control description information.

[0033] In a possible implementation manner, the method further includes:

[0034] When at least one control is displayed on the target page, in response to a trigger operation on a second control among the at least one control, a control trigger event corresponding to the second control is generated;

[0035] The control triggering event is sent to the front end, and the front end is also used to execute the first operation logic corresponding to the control triggering event.

[0036] In a possible implementation manner, the front end is further used to generate a logic request event corresponding to the second control when it is determined that the first operation logic is executed completely, and the logic request event is used to request the client to execute the second operation logic corresponding to the control trigger event;

[0037] The method further comprises:

[0038] When the logic request event sent by the front end is received, the second operation logic is executed.

[0039] The present application provides a page loading system, which includes a front end and a client;

[0040] The client is used to send page description information to the front end, where the page description information is used to describe the target page;

[0041] The front end is used to load the target page according to the page description information.

[0042] The present application provides an electronic device, the device comprising: a processor and a memory;

[0043] The memory is used to store instructions or computer programs;

[0044] The processor is used to execute the instructions or computer programs in the memory so that the electronic device executes the page loading method provided in the present application.

[0045] The present application provides a computer-readable medium, in which instructions or computer programs are stored. When the instructions or computer programs are executed on a device, the device executes the page loading method provided by the present application.

[0046] The present application provides a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the page loading method provided by the present application.

[0047] Compared with the related art, this application has at least the following advantages:

[0048] In the present application, after the front end receives the page description information sent by the client and used to describe the target page, the front end loads the target page according to the page description information, so that the front end can complete the page loading task, thereby effectively avoiding the defects that exist when the client completes the page loading task (for example, the development cost and time cost are large). Among them, because the front end completes the loading process for the target page by using the code stored in the preset storage space (for example, the cloud or a server), there is no need to store the code in advance to the terminal device deployed with the client, so it can effectively avoid the defects caused by deploying the code on the terminal device (for example, the development cost and time cost are large). BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0050] Figure 1 A flow chart of a page loading method provided in an embodiment of the present application;

[0051] Figure 2 A schematic diagram of a page loading process provided in an embodiment of the present application;

[0052] Figure 3 A flowchart of another page loading method provided in an embodiment of the present application;

[0053] Figure 4 A schematic diagram of the structure of a page loading system provided in an embodiment of the present application;

[0054] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] In order to facilitate understanding of the technical solution of the present application, some technical terms involved in the present application are explained below.

[0056] The front end is used to complete certain data processing tasks (e.g., page loading tasks, etc.) using the code stored in the preset storage space. The preset storage space refers to a pre-set code for storing some execution logic involved in the front end; and the present application does not limit the implementation method of the preset storage space, for example, it can be implemented using the cloud or server.

[0057] The client is used to complete certain data processing tasks using the code stored in the terminal device on which the client is deployed, so that different versions of code are developed for terminal devices with different operating systems to implement the execution logic of these data processing tasks.

[0058] The server is used to communicate data with the client, so that the server can provide some data information to the client, so that the client can use the data information to complete certain data processing tasks.

[0059] In addition, research has found that in some related technical solutions, the page loading task can be completed by the client, but this technical solution has the following defects: because the client may correspond to different operating systems, relevant personnel need to develop corresponding page loading tasks for different systems respectively, which makes the development cost and time cost relatively high.

[0060] Based on the above research, the present application provides a page loading method, which may specifically include: after the front end receives the page description information sent by the client to describe the target page, the front end loads the target page according to the page description information, so that the front end can complete the page loading task, thereby effectively avoiding the defects that exist when the client completes the page loading task (for example, the development cost and time cost shown in the previous paragraph are large). Among them, because the front end completes the loading process for the target page by using the code stored in the preset storage space (for example, the cloud or a server), there is no need to store the code in advance to the terminal device deployed with the client, so it can effectively avoid the defects caused by deploying the code on the terminal device (for example, the development cost and time cost are large).

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

[0062] In order to better understand the technical solution provided by the present application, the page loading method provided by the present application is described below with reference to some drawings. Figure 1 As shown, the page loading method applied to the front end provided in the embodiment of the present application includes the following S101-S102. Figure 1 A flowchart of a page loading method provided in an embodiment of the present application.

[0063] S101: The front end receives page description information sent by the client, where the page description information is used to describe a target page.

[0064] The page description information is used to describe the target page, and the target page is used to represent the page that needs to be loaded (for example, Figure 2 Page 1) is shown.

[0065] In addition, the present application does not limit the implementation method of the above page description information, for example, the page description information may at least include a page identifier of the target page. The page identifier is used to uniquely identify the page, and the present application does not limit the implementation method of the page identifier, for example, it may be implemented using a URL.

[0066] In fact, in order to better improve the page loading effect, the present application also provides another possible implementation of the above page description information. Under this implementation, if some controls need to be displayed on the above target page, the page description information not only includes the page identifier of the above target page (for example, the URL of the target page, etc.), but also includes the control description information of these controls. Among them, for any control, the control description information of the control is used to describe the control; and the present application does not limit the control description information of the control. For example, in some application scenarios, the control description information of the control can at least include the configuration information of the control (for example, the location of the control on the target page, the text displayed on the control, and other configuration information).

[0067] In addition, the present application does not limit the method for obtaining the above page description information. For example, in some application scenarios, the page description information is obtained by the client by requesting the server. For ease of understanding, an example is provided below for explanation.

[0068] As an example, the process of obtaining the above page description information may specifically include the following steps 11 to 13.

[0069] Step 11: After the client detects a page loading request for a target page, the client may generate a page information acquisition request.

[0070] The page loading request is used to request to load the target page, and the present application does not limit the implementation method of the page loading request. In addition, the present application does not limit the triggering method of the page loading request.

[0071] The page information acquisition request is used to request the server to provide the information required for loading the above target page; and this application does not limit the implementation method of the page information acquisition request.

[0072] In addition, the present application does not limit the sending method of the above page information acquisition request. For example, it can adopt an interface (for example, Figure 2 The interface shown in FIG.

[0073] Based on the relevant content of step 11 above, it can be known that for the above client, if the client detects a page loading request for the target page, the client can generate a page information acquisition request based on the page loading request, so that the page information acquisition request is used to request the server to provide the information required to load the above target page. In this way, the server can provide the information required to load the target page, thereby effectively avoiding the defects caused by the client itself providing this information (for example, defects such as large R&D costs and time costs).

[0074] Step 12: The client sends a request to obtain the above page information to the server, so that the server can respond to the request to obtain the page information and feed back page requirement information corresponding to the above target page to the client.

[0075] Among them, page requirement information refers to the information required to be used when loading the above target page; and the present application does not limit the implementation method of the page requirement information. For example, the page requirement information may at least include the page identifier of the target page, and one or more of the configuration information of some controls that need to be displayed on the target page.

[0076] Based on the relevant content of step 12 above, it can be known that for the above client, after the client generates the above page information acquisition request, the client can send the page information acquisition request to the server, so that the server can feedback the page requirement information corresponding to the above target page to the client based on the page information acquisition request, so that the page requirement information can represent the information required to be used when loading the above target page, so that the server can provide the information required to load the target page, thereby effectively avoiding the defects caused by the client itself providing this information (for example, defects such as large R&D costs and time costs).

[0077] Step 13: The client obtains the page description information of the above target page from the above page requirement information.

[0078] In the present application, for the client, after the client receives the page demand information fed back by the server, the client can obtain the page description information of the above target page from the page demand information (for example, the page demand information can be directly determined as the page description information of the target page, etc.), so that the page description information can represent the information required to be used when loading the above target page.

[0079] Based on the above steps 11 to 13, it can be seen that in some application scenarios, for the client, when the client detects that the target page needs to be loaded (for example, Figure 2 When the page 1 shown in the figure is initialized), the client can request the server through the interface for the information required to load the target page, so that the client can subsequently send the information to the front end, so that the front end can complete the page loading process for the target page based on the information. In this way, the page loading process can be implemented by the cooperation of the server, the client and the front end, which is conducive to overcoming the defects caused by the cooperation of the server and the client to implement the page loading process (for example, defects such as high development cost and time cost).

[0080] Based on the relevant content of S101 above, it can be known that in some application scenarios, in order to better improve the page loading effect, after the client obtains the page description information fed back by the server, the client does not need to use the page description information to perform page loading processing, but the client forwards the page description information to the front end, so that the front end can subsequently complete the loading processing for the target page according to the page description information.

[0081] S102: The front end loads the target page according to the page description information.

[0082] In the present application, for the front end, after the front end receives the page description information sent by the client, the front end can directly execute the page loading task according to the page description information to complete the loading process for the target page, so that the page loading task can be completed by the front end.

[0083] In addition, the present application does not limit the implementation of S102 above. For example, in a possible implementation, when the execution code of the page loading logic is stored in the preset storage space above, S102 can be specifically as follows: after the front end receives the page description information sent by the client, the front end can execute the execution code of the page loading logic according to the page description information to achieve the purpose of loading the target page. Among them, because the execution code of the page loading logic is stored in the preset storage space, rather than on the terminal device where the client is deployed, the execution code of the page loading logic does not need to be developed in different versions for different operating systems of the terminal device, which can effectively avoid the defects caused by deploying the execution code on the terminal device (such as defects such as large development costs and time costs).

[0084] Based on the relevant contents of S101 to S102 above, it can be known that for the page loading method applied to the front end provided in the embodiment of the present application, after the front end receives the page description information sent by the client and used to describe the target page, the front end loads the target page according to the page description information, so that the page loading task can be completed by the front end, thereby effectively avoiding the defects existing when the page loading task is completed by the client (for example, the development cost and time cost shown in the previous paragraph are large). Among them, because the front end completes the loading process for the target page by using the code stored in the preset storage space (for example, the cloud or a server), there is no need to store the code in advance to the terminal device deployed with the client, so that the defects caused by deploying the code on the terminal device (for example, the development cost and time cost are large) can be effectively avoided.

[0085] The study also found that in some application scenarios, a page includes not only a content area (for example, an area for displaying video data or graphic data), but also an interactive area (for example, an area for displaying some interactive controls). In addition, in some application scenarios, the controls displayed in the interactive area may be updated frequently (for example, the business logic corresponding to the existing controls is updated, new controls are added, etc.).

[0086] In order to better adapt to the control update requirements shown in the previous paragraph, the present application also provides some possible implementation methods of the above page loading method. For ease of understanding, some situations are described below.

[0087] Case 1: In some application scenarios, the front end can not only be used to perform page loading tasks, but also to display some controls on the loaded page (for example, Figure 2 button shown 1).

[0088] Based on the above situation 1, the present application also provides a possible implementation of the above page loading method applied to the front end. Under this implementation, the page loading method may include the following steps 21 to 23.

[0089] Step 21: The front end receives the page description information and the control description information sent by the client, wherein the page description information is used to describe the target page, and the control description information is used to describe the first control.

[0090] The "control description information" in step 21 above is used to describe the first control. The first control refers to the control that needs to be displayed on the target page above; and the present application does not limit the first control. For example, in some application scenarios, in order to better adapt to the frequent update requirements of some controls, the first control may refer to a dynamic control (for example, Figure 2 The button 1) shown in the figure or a newly added control. The dynamic control refers to a control that can be changed frequently. The newly added control refers to a new control added to meet new business needs.

[0091] In addition, the present application does not limit the implementation method of the "control description information" in step 21 above. For example, in one possible implementation method, the "control description information" may at least include the configuration information of the first control (for example, what text needs to be displayed on the first control, the color of the first control, the shape of the first control, and other configuration information). It should be noted that the relevant content of the configuration information can be found above, and for the sake of brevity, it will not be repeated here.

[0092] In addition, the present application does not limit the method for obtaining the "control description information" in step 21 above. For example, in some application scenarios, the "control description information" can be obtained by the client by requesting the server.

[0093] In addition, the present application does not limit the process of obtaining the "page description information and control description information" in step 21 above. For example, in some application scenarios, the process of obtaining the "page description information and control description information" may specifically include the following steps 211-213.

[0094] Step 211: After the client detects a page loading request for a target page, the client may generate a page information acquisition request.

[0095] It should be noted that for the relevant content of step 211, please refer to the relevant content of step 11 above.

[0096] Step 212: the client sends a request to obtain the above page information to the server, so that the server can respond to the page information acquisition request and feedback the page requirement information corresponding to the above target page to the client.

[0097] It should be noted that for the relevant content of step 212, please refer to the relevant content of step 12 above.

[0098] Step 213: The client obtains the page description information of the target page and the control description information of the first control from the page requirement information.

[0099] In the present application, for the client, after the client receives the page demand information fed back by the server, the client can obtain the page description information of the target page above and the control description information of the first control above from the page demand information, so that the client and the front end can subsequently complete the corresponding tasks (for example, page loading task + control display task, etc.) based on these two pieces of information.

[0100] Based on the relevant contents of steps 211 to 213 above, it can be known that in some application scenarios, the client can obtain the page description information of the target page above and the control description information of the first control above from the server through an interface request, so that the client and the front end can subsequently complete the corresponding tasks (for example, page loading task + control display task, etc.) based on these two pieces of information.

[0101] Based on the relevant content of step 21 above, it can be known that in some application scenarios, in order to better improve the page loading effect, after the client obtains the page description information and control description information fed back by the server, the client does not need to use these two pieces of information to complete the corresponding task, but the client forwards these two pieces of information to the front end so that the front end can subsequently use these two pieces of information to complete the corresponding task (for example, page loading task + control display task, etc.).

[0102] Step 22: The front end loads the target page according to the above page description information.

[0103] It should be noted that the relevant content of step 22 can be found in S102 above, and for the sake of brevity, it will not be repeated here.

[0104] Step 23: The front end displays the first control on the target page according to the control description information above.

[0105] It should be noted that the present application does not limit the correlation between the execution time of step 23 and the execution time of step 22 above. For example, in some application scenarios, the execution time of step 23 above is close to the execution time of step 22 above.

[0106] For another example, in some application scenarios, the execution time of step 23 is later than the execution time of step 22. That is, in a possible implementation, for the front end, after the front end loads the target page according to the page description information, if the first control does not exist on the loaded target page, the front end displays the first control on the loaded target page according to the control description information.

[0107] Based on the relevant content of steps 21 to 23 above, it can be seen that in some application scenarios, the above front end can not only be used to perform page loading tasks, but also can be used to display some controls (for example, dynamic buttons) on the loaded page, so as to better avoid the defects caused by completing these tasks (for example, page loading tasks + control display tasks) on the client.

[0108] Case 2: In some application scenarios, some controls may be pre-deployed on the client (for example, Figure 2The display logic of the button 1) shown in the figure is used. Therefore, in order to better reduce the development cost, there is no need to redevelop the display logic of these controls for the front end, but the client still completes the display process for these controls according to the display logic.

[0109] Based on the above situation 2, the present application also provides a possible implementation method of the above page loading method applied to the front end. Under this implementation method, when the display logic of the first control is deployed on the above client, the page loading method may include the following steps 31-33.

[0110] Step 31: The front end receives the page description information sent by the client, where the page description information is used to describe the target page.

[0111] It should be noted that for the relevant content of step 31, please refer to the relevant content of S101 above.

[0112] Step 32: The front end loads the target page according to the page description information.

[0113] It should be noted that for the relevant content of step 32, please refer to the relevant content of S102 above.

[0114] Step 33: If the front end determines that the above target page has been loaded, the front end generates a page loading completion prompt message.

[0115] The page loading completion prompt information is used to prompt that the loading process for the target page has been successfully completed on the front end.

[0116] In addition, the present application does not limit the implementation method of the above page loading completion prompt information. For example, it can be implemented using any existing or future information with a prompt function that can be transmitted between the front end and the client.

[0117] Based on the relevant content of step 33 above, it can be known that for the above front end, after the front end receives the page description information sent by the client, the front end can load the target page according to the page description information, so that after determining that the target page is loaded successfully, if the first control does not exist on the loaded target page, and the display logic of the first control is deployed on the client, it is determined that the display process for the first control can be completed by the client, so the front end can generate a page loading completion prompt information, so that the page loading completion prompt information can indicate that the target page has been loaded successfully, so that the display process for the first control can be started after the client receives the page loading completion prompt information.

[0118] Step 34: the front end sends a page loading completion prompt message to the client, and the client is used to display the first control on the target page according to the above control description information, and the control description information is used to describe the first control.

[0119] In the present application, for the client, after the client receives the page loading completion prompt information sent by the front end, the client can learn from the page loading completion prompt information that the target page has been loaded successfully, so the client can use the display logic of the first control and the control description information of the first control to display the first control on the loaded target page. In this way, the front end can execute the page loading task and the client can execute the control display task, so that some logic that has been deployed on the client can be better utilized, thereby effectively reducing development costs.

[0120] Based on the relevant contents of steps 31 to 34 above, it can be known that in some application scenarios, the front end can perform page loading tasks and the client can perform control display tasks (for example, displaying some dynamic buttons and other tasks on the loaded page), which can more effectively reduce development costs.

[0121] In fact, in some application scenarios, in order to further reduce development costs, the front end can respond to the user's triggering operation on the control. Based on this, the present application also provides a possible implementation of the page loading method applied to the front end above, in which the page loading method can at least include the following step 41.

[0122] Step 41: When at least one control is displayed on the above target page, if the front end receives a control trigger event corresponding to a second control in the at least one control sent by the client, the front end executes a first operation logic corresponding to the control trigger event.

[0123] The above "at least one control" refers to one or more controls displayed on the above target page; and the present application does not limit the implementation method of the "at least one control", for example, the "at least one control" may include all or part of the controls displayed on the target page. For another example, the "at least one control" may include the above first control.

[0124] The second control refers to the "at least one control" mentioned above, which is triggered by the user to perform some operation (for example, Figure 2 Controls for click operations or view operations, etc.) as shown.

[0125] The control trigger event corresponding to the second control is used to describe what operation the user triggers on the second control (for example, Figure 2 Click action as shown or Figure 2 viewing operations shown, etc.).

[0126] In addition, the present application does not limit the method for obtaining the control trigger event corresponding to the second control above. For example, it may specifically be: when at least one control is displayed on the target page above, the client responds to the trigger operation of the second control in the at least one control (for example, Figure 2 Click action as shown or Figure 2 The trigger operation is a view operation shown in the figure, etc.), and a control trigger event corresponding to the second control is generated, so that the control trigger event can represent the trigger operation. The trigger operation refers to the operation triggered for the second control, and the present application does not limit the trigger operation.

[0127] In addition, the "first operation logic corresponding to the control trigger event" in step 41 above refers to the business logic that is pre-set for the trigger operation described by the control trigger event and executed by the front end to respond to the trigger operation (for example, click Figure 2 After the button 1 is shown, a pop-up window will pop up on page 1, etc.)

[0128] Based on the relevant contents of step 41 above, it can be known that in some application scenarios, when at least one control is displayed on the target page above, if the client detects a trigger operation for a second control in the at least one control (for example, Figure 2 Click action as shown or Figure 2 The client can directly trigger the event corresponding to the operation (for example, Figure 2 Click event as shown or Figure 2 The view event shown in the figure) is sent to the front end, so that the front end can learn the user's trigger operation on the second control based on the event, and the front end executes the response logic corresponding to the trigger operation (for example, Figure 2 In this way, the client can detect the user operation and the front end can respond to the user operation, thereby effectively avoiding the defects caused by the client responding to the user operation (for example, the development cost and development time are relatively high).

[0129] In fact, in some application scenarios, some business logic corresponding to some controls may have been deployed on the client (for example, button state adjustment logic, etc.), so in order to further reduce development costs, the client can execute the business logic that has been deployed on it, without the need to redevelop the corresponding business logic for the front end. Based on this, the present application also provides a possible implementation method of the page loading method applied to the front end above. Under this implementation method, when the second operation logic corresponding to the control triggering event above is deployed on the client, the page loading method can at least include the above step 41 and the following steps 42-43.

[0130] Step 42: If the front end determines that the first operation logic corresponding to the above control trigger event is executed, the front end generates a logic request event corresponding to the above second control, and the logic request event is used to request the client to execute the second operation logic corresponding to the control trigger event.

[0131] The above “second operation logic corresponding to the control trigger event” refers to all the business logics that have been deployed on the client and are used to respond to the control trigger event corresponding to the second control, except for the above first operation logic (for example, Figure 2 It can be seen that, in a possible implementation, for the second control, all business logics for responding to the control trigger event corresponding to the second control can be divided into two parts, one part refers to the logic that has been deployed on the client (that is, the second operation logic), and the other part refers to the logic that has not been deployed on the client (that is, the first operation logic), so that the former can be executed by the client later, and the latter can be executed by the front end.

[0132] The logic request event corresponding to the second control is used to request the client to execute other logics (for example, Figure 2 The business logic of adjusting the state of button 1 shown, etc.).

[0133] In addition, the present application does not limit the implementation method of the above "logical request event corresponding to the second control".

[0134] Based on the relevant content of step 42 above, it can be known that for the front end, after the front end receives the control trigger event corresponding to the second control sent by the client, the front end directly executes the first operation logic corresponding to the control trigger event, so that after determining that the execution of the first operation logic is completed, if it is determined that the second operation logic corresponding to the control trigger event is deployed on the client, the front end can generate a logic request event corresponding to the second control, so that the logic request event is used to request the client to execute the second operation logic corresponding to the control trigger event, thereby achieving the purpose of responding to user operations by cooperation between the front end and the client.

[0135] Step 43: The front end sends a logic request event corresponding to the second control described above to the client, and the client is used to execute the second operation logic described above.

[0136] In the present application, for the client, after the client receives the logic request event corresponding to the second control above sent by the front end, the client can directly execute the second operation logic that has been deployed thereon, thereby achieving the purpose of responding to user operations by the cooperation of the front end and the client.

[0137] Based on the relevant contents of steps 41 to 43 above, it can be known that in some application scenarios, when the second control is being displayed on the target page, if the client detects that the user has triggered an operation on the second control, the front end may execute a portion of the response logic for the operation (for example, Figure 2 The client executes another part of the response logic for the operation (for example, Figure 2 The business logic of "adjusting the state of button 1" shown in the figure) can achieve the purpose of responding to user operations by the cooperation of the front end and the client, thereby reducing development costs while making full use of the business logic deployed on the client.

[0138] Based on the above content about the page loading method applied to the front end, it can be seen that Figure 3 As shown, the present application also provides a page loading method applied to a client, which may include the following S301-S302. Figure 3 A flowchart of another page loading method provided in an embodiment of the present application.

[0139] S301: The client receives page description information sent by the server, where the page description information is used to describe a target page.

[0140] In this application, for a client, after the client receives a page loading request for a target page, the client can first use an interface (for example, Figure 2 The interface shown in the figure sends a page information acquisition request to the server, so that the server can provide some information to the client (for example, the page description information of the target page mentioned above, etc.) in response to the page information acquisition request, so that the loading process of the target page can be completed with the help of the interaction logic between the client and the front end.

[0141] It should be noted that the relevant contents of the above S301 can be referred to the relevant contents of the above step S101, and for the sake of brevity, they will not be repeated here.

[0142] S302: The client sends page description information to the front end, and the front end is used to load the target page according to the page description information.

[0143] In this application, for the client, when the client requests the page description information of the target page above from the server (for example, Figure 2 After that, the client can send the page description information to the front end so that the front end can load the target page according to the page description information. In this way, the server and the client can assist the front end in completing the page loading task.

[0144] Based on the relevant contents of S301 to S302 above, it can be known that for the page loading method applied to the client provided in the embodiment of the present application, after the client requests the page description information used to describe the target page from the server, the client does not need to perform the page loading task for the target page, but the client directly forwards the page description information to the front end, so that the front end can perform the page loading task for the target page according to the page description information. In this way, the page loading task can be completed by the front end, thereby effectively avoiding the defects that exist when the page loading task is completed by the client (for example, the defects such as high development cost and time cost as shown in the previous paragraph).

[0145] In fact, in some application scenarios, the display logic of some controls has been deployed on the client, so in order to further reduce the R&D cost, the display logic of these controls can be executed by the client. Based on this, the present application also provides a possible implementation of a page loading method applied to the client. Under this implementation, when the display logic of the first control is deployed on the client, the page loading method can include the following steps 51 to 53.

[0146] Step 51: The client receives the page description information and the control description information sent by the server, wherein the page description information is used to describe the target page, and the control description information is used to describe the first control.

[0147] In the present application, the client can obtain the page description information of the target page and the control description information of the first control from the server through an interface request, so that the client and the front end can subsequently use these two pieces of information to complete corresponding tasks (for example, page loading tasks + control display tasks, etc.).

[0148] It should be noted that the relevant contents of the “page description information” and the “control description information” in step 51 can be found above, and for the sake of brevity, they will not be repeated here.

[0149] Step 52: The client sends the page description information to the front end, and the front end is used to load the target page according to the page description information, and when it is determined that the target page has been loaded, the front end generates a page loading completion prompt message.

[0150] In the present application, for the client, after the client requests the page description information of the above-mentioned target page from the server, the client can directly send the page description information to the front end so that the front end can load the target page according to the page description information, so that when it is determined that the target page has been loaded, that the first control does not exist on the loaded target page, and that the display logic of the first control is deployed on the client, the front end generates a page loading completion prompt information, so that the page loading completion prompt information can indicate that the target page has been loaded successfully, so that the display process for the first control can be started after the client receives the page loading completion prompt information.

[0151] Step 53: After the client receives the above page loading completion prompt information sent by the front end, the client displays the first control on the target page according to the above control description information.

[0152] In the present application, for the client, after the client receives the page loading completion prompt information sent by the front end, the client can learn from the page loading completion prompt information that the target page has been loaded successfully, so the client can use the display logic of the first control above and the control description information of the first control to display the first control on the loaded target page. In this way, the front end can execute the page loading task and the client can execute the control display task, so that some logic that has been deployed on the client can be better utilized, thereby effectively reducing development costs.

[0153] Based on the relevant contents of steps 51 to 53 above, it can be known that in some application scenarios, the front end can perform page loading tasks and the client can perform control display tasks (for example, displaying some dynamic buttons on the loaded page), which can more effectively reduce development costs.

[0154] In fact, in some application scenarios, in order to further reduce development costs, the front end can respond to the user's triggering operation on the control. Based on this, the present application also provides a possible implementation of the page loading method applied to the client above, in which the page loading method can at least include the following steps 61-62.

[0155] Step 61: When at least one control is displayed on the target page, in response to a trigger operation on a second control among the at least one control, a control trigger event corresponding to the second control is generated.

[0156] It should be noted that, for the relevant contents of "at least one control", "second control" and "control triggering event corresponding to the second control" in step 61 above, please refer to step 41 above, and for the sake of brevity, they will not be repeated here.

[0157] It should also be noted that the present application does not limit the implementation method of the "trigger operation" in step 61 above. For example, when the second control above is Figure 2 When the button 1 is shown, the "trigger operation" in step 61 can be adopted Figure 2 Click or view the operations shown.

[0158] Based on the relevant content of step 61 above, it can be known that for the client, when some controls are displayed on the target page above, if the client detects a trigger operation on a second control among these controls, the client can directly generate an event corresponding to the trigger operation so that the event can represent the trigger operation on the second control.

[0159] Step 62: The client sends the control trigger event corresponding to the second control to the front end, and the front end is also used to execute the first operation logic corresponding to the control trigger event.

[0160] In the present application, for the client, after the client generates the control trigger event corresponding to the second control above, the client can send the control trigger event to the front end, so that the front end can learn the user's trigger operation on the second control based on the event, and the front end executes the response logic corresponding to the trigger operation (for example, Figure 2 In this way, the client can detect the user operation and the front end can respond to the user operation, thereby effectively avoiding the defects caused by the client responding to the user operation (for example, the development cost and development time are relatively high).

[0161] Based on the relevant content of steps 61 to 62 above, it can be known that in some application scenarios, when some controls are displayed on the target page above, the client can detect the trigger operation for the control, and the front end can execute the response logic corresponding to the trigger operation. In this way, the client can detect the user operation and the front end can respond to the user operation, thereby effectively avoiding the defects caused by the client responding to the user operation (for example, defects such as high development cost and development time).

[0162] In fact, in some application scenarios, a certain business logic corresponding to certain controls may have been deployed on the client (for example, button state adjustment logic, etc.), so in order to further reduce development costs, the client can execute the business logic that has been deployed on it, without the need to redevelop the corresponding business logic for the front end. Based on this, the present application also provides a possible implementation method of the page loading method applied to the client above. Under this implementation method, when the second operation logic corresponding to the control triggering event above is deployed on the client, the page loading method can at least include the above step 61 and the following step 62.

[0163] Step 62: If the front end is also used to generate a logic request event corresponding to the second control above when determining that the execution of the first operation logic above is completed, then when the client receives the logic request event sent by the front end, it executes the second operation logic corresponding to the control trigger event above.

[0164] It should be noted that, for the relevant contents of "the logical request event corresponding to the second control" and "the second operation logic corresponding to the control trigger event" in step 62, please refer to the relevant contents of step 42 above. For the sake of brevity, they will not be repeated here.

[0165] Based on the relevant contents of step 62 above, it can be known that in some application scenarios, when some controls are being displayed on the target page, if the client detects that the user clicks on a control among these controls (for example, Figure 2 If a button 1) shown in the figure triggers a certain operation, the front end can execute part of the response logic for the operation (for example, Figure 2 The client executes another part of the response logic for the operation (for example, Figure 2 The business logic of "adjusting the state of button 1" shown in the figure) can reduce the development cost while making full use of the business logic deployed on the client.

[0166] Based on the page loading method provided in the embodiment of the present application, the embodiment of the present application also provides a page loading system. Figure 4 Explain and illustrate. Figure 4 This is a schematic diagram of the structure of a page loading system provided in an embodiment of the present application. It should be noted that for the technical details of the page loading system provided in an embodiment of the present application, please refer to the relevant contents of the page loading method above.

[0167] like Figure 4 As shown, the page loading system 400 provided in the embodiment of the present application includes a front end 401 and a client 402:

[0168] The client 402 is used to send page description information to the front end 401, and the page description information is used to describe the target page;

[0169] The front end 401 is used to load the target page according to the page description information.

[0170] In a possible implementation manner, the page description information includes a page identifier of the target page.

[0171] In a possible implementation, the page loading system 400 further includes a server 403 ; the page description information is obtained by the client 402 by requesting the server 403 .

[0172] In a possible implementation manner, the client 402 is further configured to receive page description information sent by the server 403 .

[0173] In a possible implementation manner, the front end 401 is further used to receive control description information sent by the client 402, where the control description information is used to describe the first control;

[0174] The front end 401 is further configured to display the first control on the target page according to the control description information.

[0175] In a possible implementation manner, the front end 401 is further configured to generate page loading completion prompt information if it is determined that the target page has been loaded;

[0176] The front end 401 is also used to send the page loading completion prompt information to the client 402;

[0177] The client 402 is further used to display the first control on the target page according to the control description information, where the control description information is used to describe the first control.

[0178] In a possible implementation manner, the control description information includes configuration information of the first control.

[0179] In a possible implementation, the page loading system 400 further includes a server 403 ; the control description information is obtained by the client 402 by requesting the server 403 .

[0180] In a possible implementation manner, the client 402 is further used to receive control description information sent by the server 403, where the control description information is used to describe the first control.

[0181] In a possible implementation manner, the client 402 is further configured to generate a control trigger event corresponding to a second control in response to a trigger operation on a second control among the at least one control when at least one control is displayed on the target page;

[0182] The client 402 is also used to send the control trigger event to the front end 401;

[0183] The front end 401 is further configured to, after receiving a control triggering event corresponding to the second control sent by the client 402, execute a first operation logic corresponding to the control triggering event.

[0184] In a possible implementation manner, the front end 401 is further used to generate a logic request event corresponding to the second control when it is determined that the first operation logic is executed, and the logic request event is used to request the client 402 to execute the second operation logic corresponding to the control trigger event;

[0185] The front end 401 is also used to send the logic request event to the client 402;

[0186] The client 402 is further configured to execute the second operation logic upon receiving the logic request event sent by the front end 401 .

[0187] Based on the relevant content of the above-mentioned page loading system 400, it can be known that for the page loading system 400 provided in the embodiment of the present application, the page loading system 400 includes a front end 401 and a client 402, and the working principle of the page loading system 400 is: after the front end 401 receives the page description information sent by the client 402 and used to describe the target page, the front end 401 loads the target page according to the page description information, so that the page loading task can be completed by the front end 401, thereby effectively avoiding the defects that exist when the page loading task is completed by the client 402 (for example, defects such as high development cost and time cost).

[0188] In addition, an embodiment of the present application also provides an electronic device, which includes a processor and a memory: the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs in the memory, so that the electronic device executes any implementation of the page loading method provided in the embodiment of the present application.

[0189] See also Figure 5 , which shows a schematic diagram of the structure of an electronic device 500 suitable for implementing the embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0190] like Figure 5As shown, the electronic device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0191] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 The electronic device 500 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0192] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0193] The electronic device provided by the embodiment of the present disclosure and the method provided by the above embodiment belong to the same inventive concept, and the technical details not fully described in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0194] The embodiment of the present application also provides a computer-readable medium, in which instructions or computer programs are stored. When the instructions or computer programs are executed on a device, the device executes any implementation of the page loading method provided in the embodiment of the present application.

[0195] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM 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 above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0196] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (Hyper Text Transfer Protocol), and may be interconnected with 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"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0197] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0198] The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device can execute the method.

[0199] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

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

[0201] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a unit / module does not, in some cases, constitute a limitation on the unit itself.

[0202] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0203] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. 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.

[0204] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0205] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0206] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0207] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0208] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A page loading method, characterized in that: The method is applied to a front end, and the method comprises: Receiving page description information sent by a client, wherein the page description information is used to describe a target page; According to the page description information, the target page is loaded.

2. The method according to claim 1, characterized in that: The page description information includes a page identifier of the target page; and / or, The page description information is obtained by the client through requesting the server.

3. The method according to claim 1, characterized in that: The method further comprises: Receiving control description information sent by the client, where the control description information is used to describe a first control; According to the control description information, the first control is displayed on the target page.

4. The method according to claim 1, characterized in that: The method further comprises: If it is determined that the target page has been loaded, a page loading completion prompt message is generated; The page loading completion prompt information is sent to the client, and the client is used to display the first control on the target page according to the control description information, and the control description information is used to describe the first control.

5. The method according to claim 3 or 4, characterized in that: The control description information includes configuration information of the first control; and / or, The control description information is obtained by the client through requesting the server.

6. The method according to claim 1, characterized in that The method further comprises: When at least one control is displayed on the target page, if a control triggering event corresponding to a second control in the at least one control sent by the client is received, a first operation logic corresponding to the control triggering event is executed.

7. The method according to claim 6, characterized in that The method further comprises: If it is determined that the first operation logic is executed completely, a logic request event corresponding to the second control is generated, where the logic request event is used to request the client to execute the second operation logic corresponding to the control trigger event; The logic request event is sent to the client, and the client is used to execute the second operation logic.

8. A page loading method, characterized in that: The method is applied to a client, and the method comprises: Receiving page description information sent by the server, wherein the page description information is used to describe the target page; The page description information is sent to a front end, and the front end is used to load the target page according to the page description information.

9. The method according to claim 8, characterized in that The receiving of the page description information sent by the server includes: Receiving page description information and control description information sent by the server, wherein the control description information is used to describe a first control; The method further comprises: After receiving the page loading completion prompt information sent by the front end, the first control is displayed on the target page according to the control description information.

10. The method according to claim 8 or 9, characterized in that: The method further comprises: When at least one control is displayed on the target page, in response to a trigger operation on a second control among the at least one control, a control trigger event corresponding to the second control is generated; The control triggering event is sent to the front end, and the front end is also used to execute the first operation logic corresponding to the control triggering event.

11. The method according to claim 10, characterized in that The front end is further used to generate a logic request event corresponding to the second control when determining that the first operation logic is executed, and the logic request event is used to request the client to execute the second operation logic corresponding to the control trigger event; The method further comprises: When the logic request event sent by the front end is received, the second operation logic is executed.

12. A page loading system, characterized in that: The page loading system includes a front end and a client; The client is used to send page description information to the front end, where the page description information is used to describe the target page; The front end is used to load the target page according to the page description information.

13. An electronic device, characterized in that: The device comprises: a processor and a memory; The memory is used to store instructions or computer programs; The processor is used to execute the instructions or computer programs in the memory so that the electronic device executes the method according to any one of claims 1 to 11.

14. A computer readable medium, characterized in that The computer-readable medium stores instructions or computer programs, and when the instructions or computer programs are executed on a device, the device executes the method according to any one of claims 1 to 11.

Images