CN114064165A

CN114064165A - Application page processing method and device

Info

Publication number: CN114064165A
Application number: CN202010772544.5A
Authority: CN
Inventors: 吴亚辉; 崔进
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-08-04
Filing date: 2020-08-04
Publication date: 2022-02-18

Abstract

The embodiment of the application discloses an application page processing method and device, wherein a client sends a page acquisition request to a service server when detecting that a target service is triggered, the service server receives the page acquisition request from the client, acquires a container page of the target service corresponding to a service identifier, acquires first page structure data of the first page, the client displays the container page after receiving the container page of the target service and the first page structure data of the first page returned by the service server, and then renders the container page according to the first page structure data to obtain the first page and displays the first page; due to the fact that the container page is introduced in the application page in an original mode, the container page comprises partial characteristics of the application page, the client replaces the waiting page with the container page after receiving the container page, and therefore a user can see partial content of the application page more quickly, and the technical problem that the waiting page is too long to display in the existing application page processing technology is solved.

Description

Application page processing method and device

Technical Field

The application relates to the field of data display, in particular to an application page processing method and device.

Background

With the popularization of mobile terminals such as mobile phones and the like, more and more users have increasingly severe dependence on the mobile terminals, in such a scenario, various service applications develop application clients, the use experience of the application clients directly influences the use interest of the users on products, and the factors influencing the use experience of the users are many, wherein the proportion of application loading time is increasing, for example, different products with the same function are realized, the loading time of a certain product is far shorter than that of other products, the user experience is greatly improved, and the user viscosity is increased.

In order to avoid frequent application switching by a user, a browser plug-in is often concentrated in an application client, so that other related functions can be opened in one application client based on the browser plug-in, for example, a user can open a member function, an interest tribe function and the like in some instant messaging software client based on the browser plug-in. When the user uses the functions, the client needs to request the corresponding page structure data from the server, and the corresponding page can be displayed after the client receives the data and renders the data based on the browser plug-in.

In practical applications, the process of requesting data by a client may take about 300 milliseconds, the process of rendering by the client also takes about 20 milliseconds, the business page can be displayed only after the page rendering is completed in the prior art, and only the waiting interface can be displayed in the middle process. The display mode causes that the display time of the waiting interface is too long, for example, about 320 milliseconds of display is shown, which also means that the user needs to wait about 320 milliseconds to see the application page, and the user experience is influenced; especially, if the function includes a plurality of pages, the user needs to wait for about 320 milliseconds each time when switching between the pages, which greatly increases the waiting time of the user and affects the user experience.

Content of application

The embodiment of the application provides an application page processing method and device, and the application page processing method and device at least solve the technical problem that the existing application page processing technology waits for a page to be displayed too long.

In order to solve the above technical problem, an embodiment of the present application provides the following technical solutions:

the embodiment of the application provides an application page processing method, which is applied to a client and comprises the following steps:

when detecting that a target service is triggered, acquiring a service identifier of the target service and a home page identifier of a home page;

sending a page acquisition request to a service server, wherein the page acquisition request carries the service identifier and the home page identifier;

receiving the container page of the target service and the home page structure data of the home page returned by the service server;

displaying the container page;

rendering according to the home page structure data to obtain a home page based on the container page;

and displaying the home page.

The embodiment of the application provides an application page processing method, which is applied to a service server and comprises the following steps:

receiving a page acquisition request from a client, wherein the page acquisition request carries a service identifier and a home page identifier;

acquiring a container page of the target service corresponding to the service identifier;

acquiring home page structure data of the home page according to the home page identifier;

and returning the container page of the target service and the home page structure data of the home page to the client.

The embodiment of the application provides an application page processing method, which comprises the following steps:

when detecting that a target service is triggered, a client acquires a service identifier of the target service and a home page identifier of a home page, and sends a page acquisition request to a service server, wherein the page acquisition request carries the service identifier and the home page identifier;

the service server receives a page acquisition request from a client, acquires a container page of a target service corresponding to the service identifier, acquires home page structure data of the home page according to the home page identifier, and returns the container page of the target service and the home page structure data of the home page to the client;

and the client receives the container page of the target service and the home page structure data of the home page returned by the service server, displays the container page, renders the container page according to the home page structure data to obtain the home page, and displays the home page.

An embodiment of the present application provides an application page processing apparatus, which is applied to a client, and includes:

the first acquisition module is used for acquiring a service identifier of a target service and a home page identifier of a home page when the target service is detected to be triggered;

a first sending module, configured to send a page obtaining request to a service server, where the page obtaining request carries the service identifier and the home page identifier;

the first receiving module is used for receiving the container page of the target service and the home page structure data of the home page returned by the service server;

the display module is used for displaying the container page;

the rendering module is used for rendering according to the home page structure data to obtain a home page based on the container page;

the display module is also used for displaying the home page.

An embodiment of the present application provides an application page processing apparatus, which is applied to a service server, and includes:

the second receiving module is used for receiving a page acquisition request from the client, wherein the page acquisition request carries a service identifier and a home page identifier;

the second acquisition module is used for acquiring a container page of the target service corresponding to the service identifier;

a third obtaining module, configured to obtain, according to the home page identifier, home page structure data of the home page;

and the second sending module is used for returning the container page of the target service and the home page structure data of the home page to the client.

The embodiment of the application provides a computer device, which comprises a processor and a memory, wherein the memory stores a plurality of instructions, and the instructions are suitable for the processor to load so as to execute the steps in the method.

The embodiment of the present application provides a computer-readable storage medium, which stores a plurality of instructions, where the instructions are suitable for a processor to load, so as to execute the steps in the above method.

Embodiments of the present application provide a computer program product or computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium; the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the steps of the method.

In the method, when a client detects that a target service is triggered, a service identifier of the target service and a home page identifier of a home page are acquired, and a page acquisition request is sent to a service server, wherein the page acquisition request carries the service identifier and the home page identifier; the service server receives a page acquisition request from a client, acquires a container page of a target service corresponding to the service identifier, acquires home page structure data of the home page according to the home page identifier, and returns the container page of the target service and the home page structure data of the home page to the client; the client receives the container page of the target service and the home page structure data of the home page returned by the service server, displays the container page, obtains the home page based on the container page according to the home page structure data rendering, and displays the home page; the method and the device have the advantages that the container page is introduced aiming at business functions, the container page comprises partial characteristics in the application page, the client replaces the waiting page with the container page after receiving the container page, so that a user can see partial contents of the application page more quickly instead of the boring waiting page, further, the pre-storage of the page structure data is completed when the user does not click other pages, the display can be directly rendered after the user clicks, the user does not need to wait for long time for obtaining the page structure data, and only needs to wait for short rendering time; when the home page is displayed, the method and the device can display the container page without excessive rendering, can avoid the overlong time for waiting for the page display, can directly render the page when the user switches the application page, do not need the time for waiting for acquiring the page structure data, have better user experience, and solve the technical problem of overlong time for waiting for the page display in the existing application page processing technology.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic networking diagram of a communication system according to an embodiment of the present application.

Fig. 2 is a schematic flowchart of an application page processing method provided in an embodiment of the present application.

Fig. 3a to fig. 3b are schematic specific flow charts of an application page processing method according to an embodiment of the present application.

Fig. 4a to 4c are schematic scene flow diagrams of an application page processing method provided in the embodiment of the present application.

Fig. 5a to 5b are schematic structural diagrams of an application page processing apparatus according to an embodiment of the present application.

Fig. 6 is a schematic structural diagram of a computer device provided in an embodiment of the present application.

Fig. 7a to 7e are schematic page views provided in the embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the embodiment of the present application, the page structure data of the page includes HTML data and the like for forming the page, which are hereinafter denoted as sphtml, the home page structure data refers to page structure data corresponding to the home page, and the non-home page structure data refers to page structure data corresponding to the non-home page; the home page refers to a first application page that a terminal needs to display after a certain function is opened by a user, while a non-home page is other application pages of the function.

In the embodiment of the present application, the container page is an intermediate interface uniquely introduced by the present application, the direct intercommunication of the multiple application pages is implemented based on the container page, which is a page obtained by abstracting all or multiple application pages of a certain function, as shown in fig. 7a, the container page only includes common page parameters of the top page shown in fig. 7b, the non-top page shown in fig. 7c, and fig. 7d, for example, only includes a page size, a page switch key below the page, and the like, the container page is also sent in the form of structural data in the process of being sent from the server to the client, but the data structure of the container page is simple, after the client receives the structural data of the container page, the drawing and rendering of the container page can be instantly completed based on the browser plug-in and is instantly shown, the drawing and rendering of the container page takes less than 1 millisecond, the display method can be ignored, so that the client can be considered to be capable of directly finishing the display of the container page after receiving the structural data of the container page, a waiting interface is replaced, and the waiting time of a user is reduced.

In the embodiment of the present application, the implementation in the field may be referred to in the processing processes of page rendering, page structure data, and the like, and details are not described in the present application. In the server, the page structure data of each page is stored corresponding to the page identification of the page.

Referring to fig. 1, fig. 1 is a schematic view of a scenario of a communication system according to an embodiment of the present application, where the system may include a user-side device and a service-side device, and the user-side device and the service-side device are connected through an internet formed by various gateways and the like, which is not described again, where the user-side device includes a plurality of terminals 11, and the service-side device includes a plurality of servers 12; wherein:

the terminal 11 includes but is not limited to portable terminals such as mobile phones and tablets, and fixed terminals such as computers, query machines and advertisement machines, and is a service port which can be used and operated by users, and in the application, the terminal provides various functions such as data query, data modification, data addition and registration for users; for the convenience of the following description, the terminal 11 is defined as a platform terminal 11a and a user terminal 11b, where the platform terminal 11a is used for a back-end operation and maintenance worker to view application running data and the like, and the user terminal 11b is installed with various application clients for a user to access various services and the like;

the server 12 provides various service services or service support for users, including a service server 12a, a storage server 12b, and the like, wherein the service server 12a is used for providing various services such as an instant messaging service, and the storage server 12b is used for providing a data storage service, performing data support for other services, and the like. In the present application, the storage server 12b may be implemented as a distributed server.

In the present application, when detecting that a target service is triggered, for example, a user opens a service link URL (Uniform Resource Locator) sent by another user, or clicks a trigger component corresponding to another function in an application client, for example, an interest placement control in a certain instant messaging client, obtains a service identifier of the target service and a home page identifier of a home page, and sends a page acquisition request to a service server, where the page acquisition request carries the service identifier and the home page identifier;

the service server 12a receives a page acquisition request from a client, acquires a container page, as shown in fig. 7a, of the target service corresponding to the service identifier, acquires the top page structure data of the top page according to the top page identifier, and returns the container page of the target service and the top page structure data of the top page to the client.

The client receives the container page of the target service and the home page structure data of the home page returned by the service server, displays the container page shown in fig. 7a, renders the home page shown in fig. 7b based on the container page according to the home page structure data, and displays the home page.

It should be noted that the system scenario diagram shown in fig. 1 is only an example, and the server and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person having ordinary skill in the art knows, with the evolution of the system and the occurrence of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

Fig. 2 is a schematic flowchart of an application page processing method according to an embodiment of the present application, please refer to fig. 2, where the application page processing method includes the following steps:

201: when detecting that a target service is triggered, a client acquires a service identifier of the target service and a home page identifier of a home page, and sends a page acquisition request to a service server, wherein the page acquisition request carries the service identifier and the home page identifier.

202: the service server receives a page acquisition request from a client, acquires a container page of a target service corresponding to the service identifier, acquires home page structure data of the home page according to the home page identifier, and returns the container page of the target service and the home page structure data of the home page to the client.

203: and the client receives the container page of the target service and the home page structure data of the home page returned by the service server, displays the container page, renders the container page according to the home page structure data to obtain the home page, and displays the home page.

Through the execution of the steps, when the client requests the home page, the server sends the container page and the home page structure data of the home page to the client, the client directly displays the container page to replace the waiting page after receiving the container page and starts to render the container page to obtain the home page, and the process is a dynamic process that the home page slowly (for example, 20 milliseconds) appears for the user, and compared with a mode that the client only replaces the waiting page to display after rendering the home page in the prior art, the user can see partial content (namely, content displayed by the container page) of the home page earlier (for example, 20 milliseconds earlier), so that the waiting time of the user is reduced.

204: and the client determines whether a non-home page exists according to the container page, and sends a non-home page acquisition request to the service server when the non-home page exists, wherein the non-home page acquisition request carries the non-home page identifier.

205: the business server receives a non-homepage acquisition request from the client, acquires non-homepage structure data of the non-homepage according to a non-homepage identifier, and sends the non-homepage structure data of the non-homepage to the client.

206: and the client receives and stores the non-homepage structure data of the non-homepage, which is sent by the service server according to the non-homepage identifier.

207: and when the client detects that the non-home page is triggered, rendering according to the non-home page structure data based on the container page to obtain and display the non-home page.

Through the execution of steps 204 to 207, the client finishes the pre-storage of the page structure data when the user does not click other pages of the service, and the corresponding non-top page can be directly rendered and displayed after the user clicks, so that the user does not need to wait for a long time for obtaining the page structure data, but only needs to wait for a short rendering time.

Specific implementations of the steps involved in the present embodiment are described below.

The embodiment provides an application page processing method, which is aimed at introducing a container page with an original service function, wherein the container page comprises partial features in the application page, and after receiving the container page, a client replaces a waiting page with the container page, so that a user can see partial contents of the application page more quickly instead of a boring waiting page, further, the pre-storage of the page structure data is completed when the user does not click other pages, the display can be directly rendered after the user clicks, the user does not need to wait for a long time for acquiring the page structure data, and only needs to wait for a short rendering time; when the home page is displayed, the method and the device can display the container page without excessive rendering, can avoid the overlong time for waiting for the page display, can directly render the page when the user switches the application page, do not need the time for waiting for acquiring the page structure data, have better user experience, and solve the technical problem of overlong time for waiting for the page display in the existing application page processing technology.

Based on the description of the overall embodiment of the communication system in the embodiment shown in fig. 2, the embodiment of the application page processing method provided in the present application will now be described with reference to the accompanying drawings.

Fig. 3a is a schematic specific flowchart of an application page processing method according to an embodiment of the present application, which specifically embodies that the method of the present application is embodied in a user terminal 11a (i.e., a client), please refer to fig. 3a, where the application page processing method includes the following steps:

301: and when detecting that the target service is triggered, acquiring a service identifier of the target service and a home page identifier of a home page.

In one embodiment, this step is one of the following: determining the service identifier and the home page identifier according to the clicked uniform resource locator; or determining the service identifier and the home page identifier from application configuration according to the clicked service function control. For example, when the user clicks the website or URL of some service, it is determined that the target service is triggered, and at this time, the client directly uses the website or content corresponding to the URL as the service identifier and the home page identifier. For another example, when the user clicks the control of the interest clan, the terminal takes the identifier of the interest clan as the service identifier of the target service, takes the page corresponding to the default open page interest circle of the interest clan configured in the client as the home page, and takes the page identifier thereof as the home page identifier. The following description will be specifically explained with reference to specific scenarios.

302: and sending a page acquisition request to a service server, wherein the page acquisition request carries the service identifier and the home page identifier.

303: and receiving the first page structure data of the container page and the first page of the target service returned by the service server.

304: and displaying the container page.

305: and based on the container page, rendering according to the home page structure data to obtain a home page.

In one embodiment, this step includes: acquiring a first page floating frame page element of the container page; controlling the container page to write the home page structure data into the home page floating frame page elements; enabling the page elements of the first page floating frame to perform page rendering according to the first page structure data to obtain the first page.

306: and displaying the home page.

The above steps 301 to 306 complete the loading of the top page, and then the preloading of other pages may be performed, that is, in an embodiment, after the step of presenting the top page, the following steps are further included: determining whether a non-home page exists according to the container page; when a non-home page exists, sending a non-home page acquisition request to the service server, wherein the non-home page acquisition request carries a non-home page identifier; receiving and storing non-homepage structure data of the non-homepage, which is sent by the service server according to the non-homepage identifier; and when the non-home page is detected to be triggered, rendering according to the non-home page structure data based on the container page to obtain and display the non-home page.

In an embodiment, the step of rendering and displaying a non-top page according to the non-top page structure data based on the container page includes: controlling the container page to dynamically create non-home page floating frame page elements; controlling the container page to write the non-home page structure data into the non-home page floating frame page elements; enabling the non-homepage floating frame page elements to perform page rendering according to the non-homepage structural data to obtain a non-homepage page; and controlling the container page to set other pages as hidden and set the non-home page as visible.

In an embodiment, before the step of sending the non-home page acquisition request to the service server, the method further includes: judging the page number of the non-home page; if the page data is smaller than the threshold value, directly sending a non-home page acquisition request to the service server; and if the page data is greater than the threshold value, sending a non-home page acquisition request corresponding to each non-home page to the service server according to a preset mode. For example, the threshold is 1.5, if there is only one non-top page, it is only necessary to directly use one ajax element to obtain the page structure data of the page, and if there are at least two non-top pages, it is only necessary to use a corresponding number of ajax elements to obtain the page structure data of the pages in parallel or sequentially.

Through the execution of the steps, the client finishes the pre-storage of the page structure data when the user does not click other pages of the service, and can directly render and display after the user clicks, so that the user does not need to wait for long time for acquiring the page structure data, but only needs to wait for short rendering time.

Fig. 3b is another specific flowchart of the application page processing method according to the embodiment of the present application, which specifically embodies the method of the present application in the service server 12a, and please refer to fig. 3b, the application page processing method includes the following steps:

311: receiving a page acquisition request from a client, wherein the page acquisition request carries a service identifier and a home page identifier.

In one embodiment, before this step, the method further comprises: acquiring all application pages contained in the target service; and constructing the container page according to the all service pages, wherein the container page at least comprises the common page parameters of all application pages of the target service.

In one embodiment, after the step of building the container page, the method further includes: and obtaining page structure data corresponding to each application page according to the page data of each application page and the page data of the container page.

312: and acquiring a container page of the target service corresponding to the service identifier.

313: and acquiring the home page structure data of the home page according to the home page identifier.

In one embodiment, this step includes: searching whether corresponding page structure data exist or not according to the home page identification of the home page; if the page structure data exists, the searched page structure data is used as the first page structure data; and if the page data does not exist, obtaining the home page structure data of the home page according to the page data of the home page and the page data of the container page. In the service server, the page structure data of the page may be pre-stored based on the page identifier, or may be obtained in real time, which will be described in detail below.

314: and returning the container page of the target service and the home page structure data of the home page to the client.

The sending of the structure data of the container page and the home page is completed through the steps, so that the client can display the related content of the home page relatively quickly.

In order to implement the pre-storage of other pages by the client, in an embodiment, after the step of returning the container page of the target service and the home page structure data of the home page to the client, the method further includes: receiving a non-home page acquisition request from the client, wherein the non-home page acquisition request carries the non-home page identifier; acquiring non-home page structure data of the non-home page; and sending the non-home page structure data of the non-home page to the client.

Based on the step, the server completes the pre-sending of other page structure data, and the client and the server do not need to communicate with each other about the page structure data in the subsequent process, so that the network burden is reduced.

On the basis of the embodiment shown in fig. 3a to 3b, only necessary minimum changes are made based on the existing pages, a plurality of pages are collected together to obtain a container page, and based on mutual drainage of the container pages, the user conversion rate is improved; the loading speed of the home page is ensured to be consistent with that of the prior art, the retention rate of a user is not influenced, and even partial content of the home page can be displayed earlier; the non-home page is loaded asynchronously, so that the white screen time of switching is greatly reduced, and the retention rate of a user is improved.

In some scenarios, all the pages related to the service are rendered by means of an iframe (floating frame, iframe element will create an inline frame containing another page). When a user opens a service page, a container page (only containing elements related to page switching) And home page structure data are requested from a server, the server can request HTML structure data (hereinafter collectively called sphtml, the data does not include structure data corresponding to the container page) of the home page in advance through ajax (Asynchronous JavaScript And XML, which is a web page development technology for creating interactive And rapid dynamic web page application And can update part of web pages without reloading the whole web page) And other modes, And the HTML structure data are returned to a browser; and the terminal browser takes out the sphtml of the home page after receiving the response, and renders through the iframe, wherein the specific mode can be as follows: the container page takes the iframe element of the container page, and then writes the sphtml into the iframe through the ifr.contentWindow.document.write (sphtml) or the ifr.contentdocument.write (sphtml), and then the browser starts to render the page by itself; after the rendering and loading of the home page is finished, the terminal requests sphtml of a non-home page from the server in modes of ajax and the like and caches the sphtml; when a user switches pages, an iframe element is dynamically created in a container page, then the sphtml is written into the iframe through the ifr.contentWindow.document.write (sphtml) or the ifr.contentdocument.write (sphtml) for rendering, meanwhile, other pages are hidden, and the user sets the page to be visible, so that the process is very fast, and the white screen switching time is greatly reduced.

The present application and the prior art will now be explained with reference to fig. 4a to 4c in a specific application scenario to clarify the technical progress and significance of the present application.

In this scenario, a service URL is sent to the current user by another user: https: // … … com/… …/yellow? … …, respectively; the user clicks on this URL to access the corresponding service. The page related to scenario 1 includes: the container page shown in fig. 7a, the member page shown in fig. 7b, the member page shown in fig. 7c, the yellow diamond page shown in fig. 7d, and the waiting page shown in fig. 7e (in practical applications, the page is a blank page).

When the user opens the service, the flow of the prior art is shown in fig. 4a, and includes the following steps:

401 to 402: and the client requests the business server for the home page structure data and finishes the rendering and display of the home page.

Referring to fig. 4c, at time t0, the user clicks the URL to enter the service interface, step 401 and step 402 are executed to complete the acquisition of the top page structure data, at this time, time goes to time t1, then top page rendering is performed, rendering is completed, and time t2 is reached, at this time, the conference page shown in fig. 7b starts to be displayed, and at time t0 to t2, for example, within 320 milliseconds, the client displays the waiting page shown in fig. 7 e.

403 to 404: and the client requests the first non-home page structure data from the service server and finishes non-home page rendering display.

Referring to fig. 4c, at time t3, the user clicks the member control of the page shown in fig. 7b to request to enter the member page, step 403 and step 404 are executed to complete the acquisition of the first non-top page structure data, at this time, time goes to time t5, then non-top page rendering is performed, rendering is completed, and time t6 is reached, at this time, the member page shown in fig. 7c starts to be displayed, and at time t3 to t6, for example, within 320 milliseconds, the client displays the waiting page shown in fig. 7e all the time.

405 to 406: and the client requests the second non-first page structure data from the service server and finishes non-first page rendering display.

Referring to fig. 4c, at time t7, the user clicks the yellow drill control of the page shown in fig. 7c, requests to enter the yellow drill page, and executes steps 405 and 406 to complete the acquisition of the second non-top page structure data, at this time, time goes to time t9, then non-top page rendering is performed, rendering is completed, and time t10 is reached, at this time, the yellow drill page shown in fig. 7d starts to be displayed, and at time t7 to t10, for example, within 320 milliseconds, the client displays the waiting page shown in fig. 7e all the time.

Based on the above description, the user needs to wait for about 320 milliseconds when switching pages.

When the user opens the service, the flow of the present application is shown in fig. 4b, and includes the following steps:

411 to 412: and the client requests the business server for the home page structure data and finishes the rendering and display of the home page.

Referring to fig. 4c, at time t0, the user clicks the URL to enter the service interface, step 411 and step 412 are executed to complete the acquisition of the container page and the top page structure data (the data is different from the data in step 402, and is marked as difference data in fig. 4b, and the container page part data is missing compared with the data in step 402), at this time, the time goes to time t1, then the top page rendering is performed, and the rendering is completed to time t2, at this time, the member page shown in fig. 7b starts to be displayed, at time t0 to t1, for example, 300 milliseconds, the client displays the waiting page shown in fig. 7e, and at time t1 to t2, for example, 20 milliseconds, the client displays the container page shown in fig. 7 a.

413 to 416: when the client displays the first page, the background acquires page structure data of other non-first pages (the data do not include structure data corresponding to the container page, and transmission of repeated data is reduced), the process lasts for about 600 milliseconds, and because the client displays the first page, a user does not sense the data acquisition process.

On the basis, rendering and displaying of other pages can be completed.

Referring to fig. 4c, at time t3, when the user clicks the affiliate control of the page shown in fig. 7b, the user requests to enter the affiliate page, the client directly performs the affiliate page rendering, the time goes to time t4, the affiliate page shown in fig. 7c starts to be displayed, and the client always displays the container page shown in fig. 7a from time t3 to time t4, for example, within 20 milliseconds.

Referring to fig. 4c, at time t7, the user clicks the yellow drill control of the page shown in fig. 7c, and requests to enter the yellow drill page, at which time the client directly performs yellow drill page rendering, and the rendering is completed to enter time t8, at which time the yellow drill page shown in fig. 7d starts to be displayed, and at time t7 to t8, for example, within 20 milliseconds, the client always displays the container page shown in fig. 7 a.

Based on the above description, the user only needs to wait for about 20 milliseconds when switching pages.

In order to implement the foregoing method, the present application also provides a corresponding application page processing apparatus, and the application page processing apparatus provided in the present application is now described with reference to the accompanying drawings.

Correspondingly, fig. 5a is a schematic structural diagram of an application page processing apparatus provided in the embodiment of the present application, which specifically embodies that the apparatus of the present application is embodied at a client, please refer to fig. 5a, where the application page processing apparatus includes the following modules:

a first obtaining module 501, configured to obtain a service identifier of a target service and a home page identifier of a home page when it is detected that the target service is triggered;

a first sending module 502, configured to send a page obtaining request to a service server, where the page obtaining request carries the service identifier and the home page identifier;

a first receiving module 503, configured to receive the container page of the target service and the home page structure data of the home page returned by the service server;

a display module 504, configured to display the container page;

a rendering module 505, configured to render, based on the container page, a home page according to the home page structure data to obtain a home page;

the display module 504 is further configured to display the home page.

In one embodiment, the rendering module 505 is specifically configured to: acquiring a first page floating frame page element of the container page; controlling the container page to write the home page structure data into the home page floating frame page elements; enabling the page elements of the first page floating frame to perform page rendering according to the first page structure data to obtain the first page.

In an embodiment, the first obtaining module 501 is specifically configured to implement one of the following manners: determining the service identifier and the home page identifier according to the clicked uniform resource locator; or determining the service identifier and the home page identifier from application configuration according to the clicked service function control.

In one embodiment, the presentation module 504, after presenting the home page, is further configured to: determining whether a non-home page exists according to the container page; when a non-home page exists, triggering the first sending module 502 to send a non-home page acquisition request to the service server, where the non-home page acquisition request carries the non-home page identifier; triggering the first receiving module 503 to receive and store the non-homepage structure data of the non-homepage sent by the service server according to the non-homepage identifier; when it is detected that the non-top page is triggered, triggering the rendering module 505 to render the non-top page according to the non-top page structure data based on the container page, and displaying the non-top page.

In one embodiment, the display module 504 is specifically configured to: controlling the container page to dynamically create non-home page floating frame page elements; controlling the container page to write the non-home page structure data into the non-home page floating frame page elements; enabling the non-homepage floating frame page elements to perform page rendering according to the non-homepage structural data to obtain a non-homepage page; and controlling the container page to set other pages as hidden and set the non-home page as visible.

In an embodiment, before sending the non-home page acquisition request to the service server, the first sending module 502 is further configured to: judging the page number of the non-home page; if the page data is smaller than the threshold value, directly sending a non-home page acquisition request to the service server; and if the page data is greater than the threshold value, sending a non-home page acquisition request corresponding to each non-home page to the service server according to a preset mode.

Correspondingly, fig. 5b is another schematic structural diagram of an application page processing apparatus provided in the embodiment of the present application, which specifically embodies the apparatus of the present application in a service server, and please refer to fig. 5b, the application page processing apparatus includes the following modules:

a second receiving module 511, configured to receive a page obtaining request from a client, where the page obtaining request carries a service identifier and a home page identifier;

a second obtaining module 512, configured to obtain a container page of the target service corresponding to the service identifier;

a third obtaining module 513, configured to obtain, according to the home page identifier, home page structure data of the home page;

a second sending module 514, configured to return, to the client, the container page of the target service and the home page structure data of the home page.

In one embodiment, as shown in fig. 5b, the apparatus further comprises: a processing module 515, configured to, before receiving a page obtaining request from a client, obtain all application pages included in the target service; and constructing the container page according to the all service pages, wherein the container page at least comprises the common page parameters of all application pages of the target service.

In one embodiment, the processing module 515, after building the container page, is further configured to: and obtaining page structure data corresponding to each application page according to the page data of each application page and the page data of the container page.

In an embodiment, the third obtaining module 513 is specifically configured to: searching whether corresponding page structure data exist or not according to the home page identification of the home page; if the page structure data exists, the searched page structure data is used as the first page structure data; and if the page data does not exist, obtaining the home page structure data of the home page according to the page data of the home page and the page data of the container page.

In one embodiment, the second receiving module 511 is further configured to: receiving a non-home page acquisition request from the client, wherein the non-home page acquisition request carries the non-home page identifier; the third obtaining module 513 is further configured to: acquiring non-home page structure data of the non-home page; the second sending module 514 is further configured to: and sending the non-home page structure data of the non-home page to the client.

Correspondingly, an embodiment of the present application further provides a computer device, where the computer device includes a server or a terminal (installed with a client), and the like, so as to implement the application page processing apparatus in any of the above embodiments.

As shown in fig. 6, the computer device may include Radio Frequency (RF) circuitry 601, memory 602 including one or more computer-readable storage media, input unit 603, display unit 604, sensor 605, audio circuitry 606, Wireless Fidelity (WiFi) module 607, processor 608 including one or more processing cores, and power supply 609. Those skilled in the art will appreciate that the computer device configuration illustrated in FIG. 6 does not constitute a limitation of computer devices, and may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components. Wherein:

the RF circuit 601 may be used for receiving and transmitting signals during a message transmission or communication process, and in particular, for receiving downlink messages from a base station and then processing the received downlink messages by one or more processors 608; in addition, data relating to uplink is transmitted to the base station. The memory 602 may be used to store software programs and modules, and the processor 608 executes various functional applications and data processing by operating the software programs and modules stored in the memory 602. The input unit 603 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

The display unit 604 may be used to display information input by or provided to a user as well as various graphical user interfaces of the computer device, which may be made up of graphics, text, icons, video, and any combination thereof.

The computer device may also include at least one sensor 605, such as a light sensor, motion sensor, and other sensors. Audio circuitry 606 includes a speaker and a microphone may provide an audio interface between a user and a computer device.

WiFi belongs to short-distance wireless transmission technology, and the computer device can help the user send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 607, which provides wireless broadband internet access for the user. Although fig. 6 shows the WiFi module 607, it is understood that it does not belong to the essential constitution of the computer device, and may be omitted entirely as needed within the scope not changing the essence of the application.

The processor 608 is a control center of the computer device, connects various parts of the entire mobile phone using various interfaces and lines, and performs various functions of the computer device and processes data by operating or executing software programs and/or modules stored in the memory 602 and calling data stored in the memory 602, thereby monitoring the mobile phone as a whole.

The computer device also includes a power supply 609 (e.g., a battery) for powering the various components, which may be logically coupled to the processor 608 via a power management system that provides management of charging, discharging, and power consumption.

Although not shown, the computer device may further include a camera, a bluetooth module, etc., which will not be described herein. Specifically, in this embodiment, the processor 608 in the computer device loads the executable file corresponding to the process of one or more application programs into the memory 602 according to the following instructions, and the processor 608 runs the application programs stored in the memory 602, so as to implement the following functions:

displaying the container page;

and displaying the home page.

Or to implement the following functions:

acquiring home page structure data of the home page;

Or to implement the following functions:

the service server receives a page acquisition request from a client, acquires a container page of a target service corresponding to the service identifier, acquires the home page structure data of the home page, and returns the container page of the target service and the home page structure data of the home page to the client;

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed description, and are not described herein again.

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.

To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to implement the following functions:

displaying the container page;

and displaying the home page.

Or to implement the following functions:

acquiring home page structure data of the home page;

Or to implement the following functions:

The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.

Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.

Since the instructions stored in the storage medium can execute the steps in any method provided in the embodiments of the present application, the beneficial effects that can be achieved by any method provided in the embodiments of the present application can be achieved, for details, see the foregoing embodiments, and are not described herein again.

To this end, embodiments of the present application provide a computer program product or a computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations described above. For example, the following functions are implemented:

displaying the container page;

and displaying the home page.

Or to implement the following functions:

acquiring home page structure data of the home page;

Or to implement the following functions:

The application page processing method and device provided by the embodiment of the present application are described in detail above, a specific example is applied in the description to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. An application page processing method is applied to a client and comprises the following steps:

displaying the container page;

and displaying the home page.

2. The method for processing an application page according to claim 1, wherein the step of rendering a top page based on the container page according to the top page structure data includes:

acquiring a first page floating frame page element of the container page;

controlling the container page to write the home page structure data into the home page floating frame page elements;

enabling the page elements of the first page floating frame to perform page rendering according to the first page structure data to obtain the first page.

3. The method for processing an application page according to claim 1, wherein the step of obtaining the service identifier of the target service and the home page identifier of the home page comprises one of the following methods:

determining the service identifier and the home page identifier according to the clicked uniform resource locator;

or determining the service identifier and the home page identifier from application configuration according to the clicked service function control.

4. The method for processing the application page according to any one of claims 1 to 3, wherein after the step of presenting the top page, the method further comprises:

determining whether a non-home page exists according to the container page;

when a non-homepage exists, sending a non-homepage acquisition request to the service server, wherein the non-homepage acquisition request carries a non-homepage identifier of the non-homepage;

receiving and storing non-homepage structure data of the non-homepage, which is sent by the service server according to the non-homepage identifier;

and when the non-home page is detected to be triggered, rendering according to the non-home page structure data based on the container page to obtain and display the non-home page.

5. The method for processing an application page according to claim 4, wherein the step of rendering and displaying a non-top page based on the container page according to the non-top page structure data comprises:

controlling the container page to dynamically create non-home page floating frame page elements;

controlling the container page to write the non-home page structure data into the non-home page floating frame page elements;

enabling the non-homepage floating frame page elements to perform page rendering according to the non-homepage structural data to obtain a non-homepage page;

and controlling the container page to set other pages as hidden and set the non-home page as visible.

6. The method for processing an application page according to claim 4, wherein before the step of sending a non-top page acquisition request to the service server, the method further comprises:

judging the page number of the non-home page;

if the page data is smaller than the threshold value, directly sending a non-home page acquisition request to the service server;

and if the page data is greater than the threshold value, sending a non-home page acquisition request corresponding to each non-home page to the service server according to a preset mode.

7. An application page processing method is applied to a service server and comprises the following steps:

8. The method for processing an application page according to claim 7, wherein before the step of receiving a page obtaining request from a client, the method further comprises:

acquiring all application pages contained in the target service;

and constructing the container page according to the all service pages, wherein the container page at least comprises the common page parameters of all application pages of the target service.

9. The application page processing method according to claim 8, further comprising, after the step of building the container page:

and obtaining page structure data corresponding to each application page according to the page data of each application page and the page data of the container page.

10. The method for processing application pages according to claim 7, wherein said step of obtaining the first page structure data of the first page comprises:

searching whether corresponding page structure data exist or not according to the home page identification of the home page;

if the page structure data exists, the searched page structure data is used as the first page structure data;

and if the page data does not exist, obtaining the home page structure data of the home page according to the page data of the home page and the page data of the container page.

11. The method for processing application pages according to any of claims 7 to 10, characterized in that after the step of returning the first page structure data of the container page and the first page of the target service to the client, the method further comprises:

receiving a non-home page acquisition request from the client, wherein the non-home page acquisition request carries a non-home page identifier of a non-home page;

acquiring non-home page structure data of the non-home page according to the non-home page identifier;

and sending the non-home page structure data of the non-home page to the client.

12. An application page processing method is characterized by comprising the following steps:

13. The application page processing method according to claim 12, further comprising:

the client determines whether a non-home page exists according to the container page, and sends a non-home page acquisition request to the service server when the non-home page exists, wherein the non-home page acquisition request carries a non-home page identifier of the non-home page;

the business server receives a non-homepage acquisition request from the client, acquires non-homepage structure data of the non-homepage according to the non-homepage identification, and sends the non-homepage structure data of the non-homepage to the client;

the client receives and stores non-homepage structure data of the non-homepage, which is sent by the service server according to the non-homepage identifier;

and when the client detects that the non-home page is triggered, rendering according to the non-home page structure data based on the container page to obtain and display the non-home page.

14. An application page processing device applied to a client side comprises:

the display module is used for displaying the container page;

the display module is also used for displaying the home page.

15. An application page processing device, applied to a service server, includes: