CN115795211A

CN115795211A - Page display method, device, system, equipment and storage medium

Info

Publication number: CN115795211A
Application number: CN202211397179.XA
Authority: CN
Inventors: 兰亚伟
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2022-11-09
Filing date: 2022-11-09
Publication date: 2023-03-14

Abstract

The embodiment of the invention discloses a page display method, a device, a system, equipment and a storage medium. The method is applied to a server and comprises the following steps: receiving a target page display request sent by a current client, wherein the target page display request comprises a target page identifier and a current client type; determining a target page template based on the current client type, the target page identifier and the type page template mapping information; determining a target data filling mode based on a target page component identification in a target page template and a mapping relation between a preset page component identification and a preset data filling mode; and based on a target data filling mode, performing data filling on the target page component, and sending the filled target page component to the current client, so that the current client performs data rendering based on the target page component filled with data, and displays the rendered target page, thereby realizing page display logic multiplexing of different types of clients, and improving flexibility.

Description

Page display method, device, system, equipment and storage medium

Technical Field

The embodiment of the invention relates to computer technology, in particular to a page display method, a device, a system, equipment and a storage medium.

Background

With the rapid development of computer technology, more and more types of clients are developed, such as Web pages, application programs APP, applets, etc., to meet the increasing user demands.

At present, each type of client is developed by copying and developing on the basis of the page display logic code of the original type, and small-range modification and adaptation are carried out in a personalized manner, so that each type of client corresponds to a set of independent page display logic code.

However, in the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art:

when a new type of client is added, a new set of page display logic codes needs to be newly developed for the server, so that the development workload is greatly increased, the maintenance cost is improved, and the development efficiency and flexibility are reduced.

Disclosure of Invention

The embodiment of the invention provides a page display method, a page display device, a page display system, page display equipment and a storage medium, which are used for realizing page display logic multiplexing of different types of clients, reducing development workload and improving development efficiency and flexibility.

In a first aspect, an embodiment of the present invention provides a page display method, applied to a server, including:

receiving a target page display request sent by a current client, wherein the target page display request comprises a target page identifier and a current client type corresponding to the current client;

determining a target page template corresponding to the target page display request based on the current client type, the target page identifier and pre-configured type page template mapping information;

determining a target data filling mode corresponding to a target page component in the target page template based on a target page component identifier in the target page template and a mapping relation between a preset page component identifier and a preset data filling mode;

and based on the target data filling mode, performing data filling on the target page assembly, and sending the target page assembly subjected to data filling to the current client, so that the current client performs data rendering based on the target page assembly subjected to data filling, and displays a rendered target page.

In a second aspect, an embodiment of the present invention further provides a page display method, applied to a client, including:

generating a target page display request based on the target page identification and the current client type corresponding to the current client;

sending the target page display request to a server, so that the server determines a target page template corresponding to the target page display request based on the current client type, the target page identifier and preset type page template mapping information, determines a target data filling mode corresponding to a target page component in the target page template based on a target page component identifier in the target page template and a mapping relation between the preset page component identifier and a preset data filling mode, and performs data filling on the target page component based on the target data filling mode;

and performing data rendering on the basis of the target page component filled with the data sent by the server, and displaying the rendered target page.

In a third aspect, an embodiment of the present invention further provides a page display apparatus, integrated in a server, including:

the system comprises a target page display request receiving module, a target page display request receiving module and a target page display request sending module, wherein the target page display request receiving module is used for receiving a target page display request sent by a current client, and the target page display request comprises a target page identifier and a current client type corresponding to the current client;

a target page template determining module, configured to determine, based on the current client type, the target page identifier, and preconfigured type page template mapping information, a target page template corresponding to the target page display request;

the target data filling mode determining module is used for determining a target data filling mode corresponding to a target page component in the target page template based on a target page component identifier in the target page template and a mapping relation between a preset page component identifier and a preset data filling mode;

and the data filling module is used for performing data filling on the target page component based on the target data filling mode, and sending the target page component after the data filling to the current client, so that the current client performs data rendering based on the target page component after the data filling, and displays a rendered target page.

In a fourth aspect, an embodiment of the present invention further provides a page display apparatus, integrated in a client, including:

the target page display request generation module is used for generating a target page display request based on the target page identification and the current client type corresponding to the current client;

a target page display request sending module, configured to send the target page display request to a server, so that the server determines a target page template corresponding to the target page display request based on the current client type, the target page identifier, and pre-configured type page template mapping information, determines a target data filling manner corresponding to a target page component in the target page template based on a target page component identifier in the target page template and a mapping relationship between the pre-configured page component identifier and a preset data filling manner, and performs data filling on the target page component based on the target data filling manner;

and the data rendering module is used for performing data rendering on the target page component filled with the data sent by the server and displaying the rendered target page.

In a fifth aspect, an embodiment of the present invention further provides a page display system, where the system includes: a server and different types of clients;

wherein, the server is used for realizing the page display method provided by the first aspect;

each of the clients is used for realizing the page display method provided by the second aspect.

In a sixth aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:

one or more processors;

a memory for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the page presentation method provided by any embodiment of the invention.

In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the page display method provided in any embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits:

the server determines a target page template corresponding to a target page display request according to a current client type and a target page identifier in the target page display request sent by a current client and pre-configured type page template mapping information, determines a target data filling mode corresponding to a target page component in the target page template based on the target page component identifier in the target page template and a mapping relation between the pre-configured page component identifier and a preset data filling mode, fills data in the target page component based on the target data filling mode, sends the target page component after the data filling to the current client, and renders data based on the target page component after the data filling by the current client and displays the rendered target page.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description will be given below of the drawings required for the embodiments or the technical solutions in the prior art, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

FIG. 1 is a flowchart of a page display method according to an embodiment of the present invention;

FIG. 2 is an example of a service architecture of a page presentation system according to an embodiment of the present invention;

FIG. 3 is a flowchart of a page display method according to an embodiment of the present invention;

FIG. 4 is an example of a response process to a target page show request according to an embodiment of the present invention;

FIG. 5 is a flowchart of a page display method according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a page displaying apparatus according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a page displaying apparatus according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a page display system according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Fig. 1 is a flowchart of a page displaying method according to an embodiment of the present invention, which is applicable to displaying pages on different types of clients. The method can be executed by a page presentation device, which can be implemented by software and/or hardware, and is integrated in a server. As shown in fig. 1, the method specifically includes the following steps:

s110, receiving a target page display request sent by the current client, wherein the target page display request comprises a target page identifier and a current client type corresponding to the current client.

A client may refer to a program that provides local services to a client. Different types of individual clients may be clients that implement the same software functionality with different access portals. For example, the page-showing functionality may be implemented with an application APP, applet, web-page web, etc. type client. Different types of clients can be installed on different devices, such as a desktop computer, a mobile phone, a tablet computer, a notebook computer, and the like. The current client in this embodiment may refer to a client that sends a page presentation request at the current time among all types of clients.

The target page display request can be used for requesting the server to display the target page. The target page identification may be identification information uniquely characterizing the target page so as to distinguish different pages. The current client type may refer to access portal information corresponding to the current client, such as an application APP, an applet, or a web page web.

Specifically, when a target page needs to be displayed by each type of client, a target page display request may be generated based on the target page identifier and the current client type corresponding to the current client, and the target page display request may be sent to the server, so that the server may receive the target page display request sent by the current client. It should be noted that, if the server receives multiple target page display requests sent by multiple clients at the same time, the server may perform response processing for each target page display request.

Exemplarily, after S110, the method may further include: and performing Token verification on the target page display request based on the current client type in the target page display request and a current Token corresponding to the current client, and executing subsequent S120 operation when the verification is successful.

Specifically, through Filter filtering, in implementing a Filter interface, a current client type may be matched with all currently supported client types, if matching is successful, it is indicated that the current client type is a client type allowed to be accessed, at this time, the current Token may be continuously matched with a preset Token corresponding to the current client type, if matching is successful, it is indicated that the current client is a client with a normal identity, at this time, subsequent operations may be continued. Fig. 2 shows an example of a service architecture of a page presentation system. As shown in fig. 2, the anti-flushing current limit can provide guarantee for the degraded disaster recovery service of the entire system, and prevent the occurrence of malicious service requests and abnormal identity calling terminals, which may cause a situation that the service is crashed due to inaccurate flow estimation. The embodiment can be realized by using a self-contained client token current limiting and anti-brushing function called by JSF (Java Server Faces, a standard framework for constructing Java Web application programs) remote service.

And S120, determining a target page template corresponding to the target page display request based on the current client type, the target page identification and the preset type page template mapping information.

The page content can be divided in advance, and the page contents belonging to the same service attribute in the page are aggregated to one page component. For example, content in the page related to order status may all be aggregated into the order status component; aggregating the content related to the delivery information into a delivery information component; aggregating content related to item prices into an item price component, and so on. Different pages can have the same display content, so that the divided page components can be multiplexed to realize the co-construction of page display services. Each page corresponds to a page template. The page template may include one or more page components, which may be specifically determined based on the content of the page. The content of the same page in different types of clients can be the same, so that the page template of the same page in different types of clients can comprise the same page component, or the page template of different pages in the same type of clients can comprise the same page component, so that the reuse of the page components can be realized. The page template mapping information may be obtained by configuring a corresponding page template for each page in advance based on the content of each page displayed on each type of client. The page template mapping information may refer to a mapping relationship among a client type, a page identifier, and a page template. The target page template may refer to a page template that is required to be used to present the target page.

Specifically, the server may match the current client type and the target page identifier with pre-configured type page template mapping information, and determine a target page template corresponding to the target page identifier in the current client type. As shown in fig. 2, corresponding page template mapping information can be configured in the configuration center based on the display requirements of the clients of each type, so that dynamic configuration and customization of the types can be realized, and personalized requirements can be met. It should be noted that, if a new type of client needs to be added, corresponding page template mapping information may be added in the configuration center, and the display logic code does not need to be modified, so that application co-construction may be implemented, and flexibility is improved. The configuration center can be specifically realized by zookeeper.

Exemplarily, S120 may include: determining target page template mapping information corresponding to the current client type based on the current client type and a mapping relation between a preset client type and preset page template mapping information; and determining a target page template corresponding to the target page display request based on the target page identifier and the mapping relation between the page identifier in the target page template mapping information and the preset page template.

The type page template mapping information may include: and mapping relation between the client type and the preset page template mapping information. The preset page template mapping information may include: and mapping relation between the page identification and the preset page template. The target page template mapping information may refer to preset page template mapping information corresponding to the current client type.

Specifically, the preset page template mapping information corresponding to the current client type may be determined as the target page template mapping information corresponding to the current client type based on a mapping relationship between the preconfigured client type and the preset page template mapping information. And determining the preset page template corresponding to the target page identifier as a target page template corresponding to the current client type, namely a target page template corresponding to the target page display request, based on the mapping relation between the page identifier in the target page template mapping information and the preset page template.

Illustratively, the type page template mapping information may include: and mapping relation between the page identification and the preset type template mapping information. The preset type template mapping information may include a mapping relationship between a client type and a preset page template. Based on the method, the target type template mapping information corresponding to the target page identifier can be determined based on the target page identifier and the mapping relation between the page identifier and the preset type template mapping information; and determining a target page template corresponding to the target page display request based on the mapping relation between the client type in the current client type and target type template mapping information and a preset page template. In this embodiment, the mapping order among the client type, the page identifier, and the page template in the page template mapping information is not limited.

S130, determining a target data filling mode corresponding to the target page component in the target page template based on the target page component identification in the target page template and the mapping relation between the preset page component identification and the preset data filling mode.

The target page template may include one or more target page components, among other things. The target page component identification may be identification information for uniquely identifying the target page component to distinguish different page components. The preset data filling manner may be a preset manner for filling the component data in the specific page component. For example, a corresponding preset data filling manner may be set based on the data filling logic of each page component, and a mapping relationship between the page component identifier and the preset data filling manner may be configured in advance.

Specifically, for each target page component in the target page template, the preset data filling manner corresponding to the target page component identifier corresponding to the target page component may be determined as the target data filling manner corresponding to the target page component based on a mapping relationship between a pre-configured page component identifier and the preset data filling manner, so that the target data filling manner corresponding to each target page component may be determined.

And S140, based on the target data filling mode, performing data filling on the target page component, and sending the target page component after the data filling to the current client, so that the current client performs data rendering based on the target page component after the data filling, and displays the rendered target page.

Specifically, the server can perform data filling on corresponding target page components according to data filling logics corresponding to each target data filling mode, and send the target page components after the data filling to the current client, so that the current client can perform data rendering on the target page components after the data filling and display the rendered target pages, thereby performing unified display on pages for different types of clients, solving the problem of repeated logic polishing construction, realizing multiplexing and configurability of page display logics, achieving the effects of one-end development and multi-end application, providing flexible service customization, reducing machine cost and maintenance cost, laying a foundation for subsequent new client type development and construction, greatly improving development efficiency of new types, and realizing high availability, high multiplexing and high configurability of middle data logics and co-construction business logics.

For example, the "data filling the target page component based on the target data filling manner" in S140 may include: and performing data filling on the target page component by calling a data filling function in the target data filling implementation class corresponding to the target data filling mode.

Wherein each data filling mode corresponds to one data filling implementation class. The data filling implementation class can inherit the data filling interface and overwrite the data filling function in the data filling interface, so that the data filling function in the data filling implementation class can realize the data filling function of the corresponding page component. Specifically, data filling can be performed on the target page component by calling a data filling function in the target data filling implementation class, so that the data filling efficiency can be improved.

Illustratively, the middle station in fig. 2 stores and processes data, so that the data and the service logic are decoupled, and the back end becomes the front-middle station difference. The method comprises the steps of splitting a module assembly for a client application service logic, building a co-building application, and realizing multiplexing of a multi-channel service logic and customized configuration of a related module.

According to the technical scheme of the embodiment, the server determines a target page template corresponding to a target page display request according to a current client type and a target page identifier in the target page display request sent by a current client and preset type page template mapping information, determines a target data filling mode corresponding to the target page component in the target page template based on the target page component identifier in the target page template and a mapping relation between the preset page component identifier and a preset data filling mode, fills data in the target page component based on the target data filling mode, sends the target page component after data filling to the current client, and renders data based on the target page component after data filling by the current client and displays a rendered target page.

On the basis of the foregoing technical solution, "sending the target page component after data filling to the current client in S140, so that the current client performs data rendering based on the target page component after data filling and displays a rendered target page", may include: acquiring target page style information corresponding to a target page template; and sending the target page component and the target page style information which are subjected to data filling to the current client so as to enable the current client to perform data rendering based on the target page component and the target page style information which are subjected to data filling, and displaying the rendered target page.

Each page template corresponds to one piece of page style information, and the page style information may refer to specific style information of the page template, for example, page component display sequence information, component dividing line information, and the like in the page template. The page style information may also be identification information for a unique page style so as to distinguish different page styles using the page style identification information.

Specifically, corresponding page sample information may be configured for each page template in advance, and a mapping relationship between the page template and the page style information is established, so that, based on the mapping relationship, target page style information corresponding to the target page template may be obtained, and the target page component and the target page style information after data filling are simultaneously sent to the current client, so that the current client performs data rendering on the target page component after data filling according to the target page style information to show a target page under the target page style, or the original page style information corresponding to the current client may be compared with the target page style information, if the two are not consistent, the target page component after data filling sent by the server may be subjected to data division and integration to obtain the target page component corresponding to the original page style information, and the target page component corresponding to the original page style information is subjected to data rendering to show the target page under the original page style, thereby realizing adaptation of the page style and satisfying personalized requirements.

On the basis of the technical scheme, the method further comprises the following steps: determining a data filling implementation class based on a preset text file corresponding to a data filling interface by calling an implementation class query function, wherein the file name of the preset text file is a fully-limited name of the data filling interface, and the fully-limited name of the data filling implementation class is stored in the preset text file; and rewriting the data filling function in the data filling implementation class by calling a rewriting interface.

The implementation class query function may refer to a function for querying an implementation class of the implementation interface. For example, the implementation-class query function may refer to a load () function in a java.util.serviceloader component in a JDK software tool. The preset text file corresponding to the data filling interface can be a UTF-8 text file named by a fully qualified name of the interface. And writing all the corresponding limited names of all the data filling implementation classes in the preset text file, and if a plurality of data filling implementation classes exist, separating the limited names of all the data filling implementation classes by line feed characters.

Specifically, when the data filling logic is required, a packet of the data filling implementation class can be introduced, a class implementation query function is called, specific service implementation is queried and loaded based on a preset text file corresponding to the data filling Interface, and after the class implementation of the data filling is loaded, a rewriting Interface SPI (Serial Peripheral Interface) can be called to rewrite the data filling function in the class implementation of the data filling, so that the data filling logic can be dynamically adjusted, the flexibility is improved, and the personalized display requirement is met.

Fig. 3 is a flowchart of a page display method according to an embodiment of the present invention, in which, on the basis of the foregoing embodiments, a target page display request further includes a current service state, and on this basis, a target page template corresponding to the target page display request is determined based on a current client type, a target page identifier, and preconfigured type page template mapping information. Wherein explanations of the same or corresponding terms as those of the above embodiments are omitted.

Referring to fig. 3, the page display method provided in this embodiment specifically includes the following steps:

s310, receiving a target page display request sent by the current client, wherein the target page display request comprises the current service state, a target page identifier and the current client type corresponding to the current client.

The current service state may refer to a service state when a target page is requested to be displayed in a current client. For example, if the request is to present an order details page, the current order status may be categorized as either a completed status or a cancelled status.

S320, determining a target page template corresponding to the target page display request based on the current client type, the target page identification, the current service state and the preset type state page template mapping information.

The type state page template mapping information may refer to a mapping relationship between a client type, a service state, a page identifier, and a page template. The embodiment can generate different page templates aiming at different business states in the same page, so that the page templates only comprise page components matched with the business states, and the page components unmatched with the business states are removed, thereby further improving the data filling efficiency and further improving the page display efficiency. For example, the order details page may correspond to a completed template and a cancelled template, wherein the completed template includes only page components that need to be exposed when the order is completed. The cancelled template only comprises page components required to be displayed when the order is cancelled.

Specifically, the server can match the current client type, the target page identifier and the current service state with the pre-configured type page template mapping information, and determine the target page template in the current service state corresponding to the target page identifier under the current client type, so that the page component in the target page template, which is not matched with the current service state, can be removed in advance, data filling of the page component, which is not matched with the current service state, which is not required to be displayed, is avoided, data filling is only performed on the page component, which is required to be displayed, and therefore, the data filling efficiency can be improved, further, the response time is reduced, and the page display efficiency is improved.

Exemplarily, S320 may include: determining target state page template mapping information corresponding to the current client type based on the current client type and a mapping relation between the preset client type and preset state page template mapping information; determining target state template mapping information corresponding to the target page identifier based on the mapping relation between the target page identifier and the page identifier in the target state page template mapping information and preset state template mapping information; and determining a target page template corresponding to the target page display request based on the current business state and the mapping relation between the business state in the target state template mapping information and the preset page template.

The type state page template mapping information may include: and mapping relation between the client type and the preset state page template mapping information. The preset state page template mapping information may include: and mapping relation between the page identification and the preset state template mapping information. The preset state template mapping information may include: and mapping relation between the service state and the preset page template.

Specifically, the preset state page template mapping information corresponding to the current client type may be determined as the target state page template mapping information corresponding to the current client type based on a mapping relationship between the preconfigured client type and the preset state page template mapping information. And determining preset state template mapping information corresponding to the target page identifier as target state template mapping information corresponding to the current client type based on the mapping relation between the page identifier in the target state page template mapping information and the preset state template mapping information. And determining the preset page template corresponding to the current service state as a target page template corresponding to the current client type, namely a target page template corresponding to the target page display request, based on the mapping relation between the service state in the target state template mapping information and the preset page template.

It should be noted that, in the present embodiment, the mapping order between the client type, the service state, the page identifier, and the page template in the type state page template mapping information is not limited, and may be any implementation manner capable of mapping the target page template.

S330, determining a target data filling mode corresponding to the target page component in the target page template based on the target page component identifier in the target page template and the mapping relation between the preset page component identifier and the preset data filling mode.

And S340, based on the target data filling mode, performing data filling on the target page component, and sending the target page component after the data filling to the current client, so that the current client performs data rendering based on the target page component after the data filling, and displays the rendered target page.

Illustratively, fig. 4 gives an example of a response process to a target page presentation request. As shown in fig. 4, a certain client sends an order page display request to a server, and the server may determine a target page template, such as a completed template or a cancelled template, corresponding to the order page display request based on the type state page template mapping information of the configuration center and based on the current client type, the order page identifier, and the current service state in the order page display request. Based on a target data filling mode corresponding to each target page component in the target page template, the target page components are filled with data by utilizing component data stored in a database, all the filled target page components are returned to the client, and the client can render and display the received target page components in a data automatic assembly mode, so that the data filling efficiency can be improved by determining the page templates in different service states, the response time is further reduced, and the page display efficiency is improved.

According to the technical scheme, the current client type, the target page identification and the current service state are matched with the pre-configured type page template mapping information through the server, the target page template in the current service state corresponding to the target page identification under the current client type is determined, so that the page component in the target page template, which is not matched with the current service state, can be removed in advance, the page component, which is not matched with the current service state, is prevented from being filled with data, namely the page component which does not need to be displayed is not filled with data, only the page component which needs to be displayed is filled with data, the data filling efficiency can be improved, the response time is shortened, and the page display efficiency is improved.

Fig. 5 is a flowchart of a page displaying method according to an embodiment of the present invention, which is applicable to displaying pages on different types of clients. The method can be executed by a page-showing device, which can be implemented by means of software and/or hardware, integrated in each type of client. As shown in fig. 5, the method specifically includes the following steps:

s510, generating a target page display request based on the target page identification and the current client type corresponding to the current client.

The client may refer to a program that provides local services for the client. Different types of individual clients may be clients that implement the same software functionality with different access portals. For example, the page-showing functionality may be implemented with an application APP, applet, web-page web, etc. type client. Different types of clients can be installed on different devices, such as a desktop computer, a mobile phone, a tablet computer, a notebook computer, and the like. The current client in this embodiment may refer to a client that sends a page presentation request at the current time among all types of clients.

Specifically, when a target page needs to be displayed by each type of client, a target page display request may be generated based on the target page identifier and the current client type corresponding to the current client.

S520, the target page display request is sent to the server, so that the server determines a target page template corresponding to the target page display request based on the current client type, the target page identification and the preset type page template mapping information, determines a target data filling mode corresponding to the target page component in the target page template based on the target page component identification in the target page template and the mapping relation between the preset type page component identification and the preset data filling mode, and fills data in the target page component based on the target data filling mode.

Specifically, the current client sends a target page display request to the server, so that the server can receive the target page display request sent by the current client, match the current client type and the target page identifier in the target page display request with the pre-configured type page template mapping information, determine a target page template corresponding to the target page identifier in the current client type, and determine a preset data filling mode corresponding to the target page component identifier corresponding to the target page component as a target data filling mode corresponding to the target page component based on the mapping relationship between the pre-configured page component identifier and the preset data filling mode. The server can perform data filling on the corresponding target page component according to the data filling logic corresponding to each target data filling mode, and send the target page component after the data filling to the current client.

S530, data rendering is carried out on the target page component filled with the data sent by the server, and the rendered target page is displayed.

Specifically, the current client can render data through a target page component filled with the data and display the rendered target page, so that the page can be uniformly displayed for different types of clients, the problem of repeated construction of logic polishing is solved, multiplexing and configurability of page display logic are realized, the effects of one-end development and multi-end application are achieved, flexible service customization is provided, the machine cost and the maintenance cost are reduced, a foundation is laid for subsequent new client type development and construction, the development efficiency of a new type is greatly improved, and high availability, high multiplexing and high configurability of the middle station data logic and the co-construction service logic are realized.

Exemplarily, S530 may include: if the static data identification information exists in the target page component after the data filling sent by the server, generating a static data acquisition request based on the static data identification information, and sending the static data acquisition request to the distributed server; and acquiring the static data returned by the distributed server based on the static data acquisition request.

The static data may refer to static file data that does not dynamically change with time, such as pictures. The static data identification information may be used to uniquely identify the static data in order to distinguish between different static data. The distributed server may be a server for distributed storage of static data. For example, the Distributed server can be, but is not limited to, a Distributed File System, fastDFS (Distributed File System).

Specifically, the static data in the target page component data can be stored in the distributed server in advance, so that when the static data is filled in the target page component, only the static data identification information corresponding to the static data needs to be filled, and only the filled static data identification information replaces the static data to be sent to the current client, so that the response data volume can be reduced, the data transmission time is shortened, and the data response efficiency is further improved. When the current client detects that the static data identification information exists in the target page component, a static data acquisition request containing the static data identification information can be generated and sent to the distributed server. The distributed server can inquire the static data corresponding to the static data identification information and return the static data to the current client, so that the current client can render the static data and display the corresponding static data. By storing the static data into the distributed server, when the static data needs to be modified, the static data can be directly modified in the distributed server without upgrading the version of the client, so that the modification efficiency and the flexibility can be improved.

On the basis of the technical scheme, the method further comprises the following steps: receiving target page style information corresponding to a target page template sent by a server; correspondingly, the data rendering based on the target page component filled with the data sent by the server may include: and performing data rendering based on the target page component and the target page style information which are filled by the data sent by the server.

Specifically, corresponding page sample information may be configured for each page template in advance, and a mapping relationship between the page template and the page style information is established, so that target page style information corresponding to the target page template may be obtained based on the mapping relationship, and the target page component after data filling is also sent to the current client, so that the current client may perform data rendering on the target page component after data filling according to the target page style information, and display the target page in the target page style.

Illustratively, data rendering based on the target page component and the target page style information after data filling sent by the server may include: comparing original page style information corresponding to the current client with target page style information; and if the original page style information is inconsistent with the target page style information, carrying out data division and integration on a target page component filled with data sent by the server based on the inconsistent page style, obtaining the target page component corresponding to the original page style information, and carrying out data rendering on the target page component corresponding to the original page style information.

Specifically, the current client can compare the original page style information with the target page style information, if the original page style information and the target page style information are not consistent, the target page component filled with data sent by the server can be subjected to data division and integration according to the inconsistent page style, the target page component corresponding to the original page style information is obtained, data rendering is carried out on the target page component corresponding to the original page style information, and the target page under the original page style is displayed, so that the adaptation of the page style is realized, and the personalized requirement is met.

The following is an embodiment of the page display apparatus integrated in the server according to the embodiment of the present invention, which belongs to the same inventive concept as the above-mentioned page display method applied to the server, and reference may be made to the above-mentioned embodiment of the page display method applied to the server for details that are not described in detail in the embodiment of the page display apparatus.

Fig. 6 is a schematic structural diagram of a page displaying apparatus according to an embodiment of the present invention, which is applicable to displaying pages on different types of clients. As shown in fig. 6, the apparatus is integrated in a server, and specifically includes: a target page display request receiving module 610, a target page template determining module 620, a target data filling mode determining module 630 and a data filling module 640.

The target page display request receiving module 610 is configured to receive a target page display request sent by a current client, where the target page display request includes a target page identifier and a current client type corresponding to the current client; a target page template determining module 620, configured to determine, based on the current client type, the target page identifier, and preconfigured type page template mapping information, a target page template corresponding to the target page display request; a target data filling manner determining module 630, configured to determine a target data filling manner corresponding to a target page component in the target page template based on a mapping relationship between a target page component identifier in the target page template and a preconfigured page component identifier and a preset data filling manner; and the data filling module 640 is configured to perform data filling on the target page component based on the target data filling manner, and send the target page component after data filling to the current client, so that the current client performs data rendering based on the target page component after data filling, and displays a rendered target page.

Optionally, the target page template determining module 620 is specifically configured to:

determining target page template mapping information corresponding to the current client type based on the current client type and a mapping relation between a preset client type and preset page template mapping information; and determining a target page template corresponding to the target page display request based on the target page identifier and the mapping relation between the page identifier in the mapping information of the target page template and a preset page template.

Optionally, the target page display request further includes a current service state;

the target page template determining module 620 is further configured to: and determining a target page template corresponding to the target page display request based on the current client type, the target page identifier, the current service state and preset type state page template mapping information.

Optionally, the target page template determining module 620 is further specifically configured to:

determining target state page template mapping information corresponding to the current client type based on the current client type and a mapping relation between a preset client type and preset state page template mapping information; determining target state template mapping information corresponding to the target page identifier based on the target page identifier and a mapping relation between the page identifier in the target state page template mapping information and preset state template mapping information; and determining a target page template corresponding to the target page display request based on the current business state and the mapping relation between the business state in the target state template mapping information and a preset page template.

Optionally, the data padding module 640 is specifically configured to: and performing data filling on the target page component by calling a data filling function in a target data filling implementation class corresponding to the target data filling mode.

Optionally, the apparatus further comprises:

the rewriting module is used for determining a data filling implementation class based on a preset text file corresponding to a data filling interface by calling an implementation class query function, wherein the file name of the preset text file is a full-limited name of the data filling interface, and the full-limited name of the data filling implementation class is stored in the preset text file; and rewriting the data filling function in the data filling implementation class by calling a rewriting interface.

Optionally, the data padding module 640 is further specifically configured to:

acquiring target page style information corresponding to the target page template; and sending the target page assembly subjected to data filling and the target page style information to the current client so as to enable the current client to perform data rendering based on the target page assembly subjected to data filling and the target page style information and display a rendered target page.

The page display device provided by the embodiment of the invention can execute the page display method applied to the server provided by the embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the page display method.

It should be noted that, in the embodiment of the page displaying apparatus, the units and modules included in the embodiment are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, the specific names of the functional units are only for the convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.

The following is an embodiment of the page display apparatus integrated in the client according to an embodiment of the present invention, and the apparatus and the page display method applied to the client belong to the same inventive concept, and details that are not described in detail in the embodiment of the page display apparatus may refer to the above embodiment of the page display method applied to the client.

Fig. 7 is a schematic structural diagram of a page displaying apparatus according to an embodiment of the present invention, which is applicable to displaying pages on different types of clients. As shown in fig. 6, the apparatus is integrated in the client, and specifically includes: a destination page display request generating module 710, a destination page display request transmitting module 720, and a data rendering module 730.

The target page display request generating module 710 is configured to generate a target page display request based on the target page identifier and a current client type corresponding to a current client; a target page display request sending module 720, configured to send the target page display request to a server, so that the server determines a target page template corresponding to the target page display request based on the current client type, the target page identifier, and pre-configured type page template mapping information, determines a target data filling manner corresponding to a target page component in the target page template based on a mapping relationship between a target page component identifier in the target page template and a pre-configured page component identifier and a preset data filling manner, and performs data filling on the target page component based on the target data filling manner; and a data rendering module 730, configured to perform data rendering on the target page component filled with the data sent by the server, and display a rendered target page.

Optionally, the data rendering module 730 is specifically configured to:

if static data identification information exists in the target page component after data filling sent by the server, generating a static data acquisition request based on the static data identification information, and sending the static data acquisition request to a distributed server; and acquiring the static data returned by the distributed server based on the static data acquisition request.

Optionally, the apparatus further comprises:

the target page style information receiving module is used for receiving target page style information corresponding to the target page template sent by the server;

a data rendering module 730, further configured to: and performing data rendering based on the target page assembly filled with the data sent by the server and the target page style information.

Optionally, the data rendering module 730 is further specifically configured to:

comparing the original page style information corresponding to the current client with the target page style information; and if the original page style information is inconsistent with the target page style information, performing data division and integration on a target page component filled with data sent by the server based on the inconsistent page style to obtain a target page component corresponding to the original page style information, and performing data rendering on the target page component corresponding to the original page style information.

The page display device provided by the embodiment of the invention can execute the page display method applied to the client terminal provided by the embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the page display method.

It should be noted that, in the embodiment of the page displaying apparatus, the units and modules included in the embodiment are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.

Fig. 8 is a schematic structural diagram of a page display system according to an embodiment of the present invention, which is applicable to a case where pages are displayed on different types of clients. As shown in fig. 8, the system includes: a server 810 and different types of clients 820.

Wherein each client 820 and the server 810 can be communicatively connected through a network service for data transmission. The server 810 is configured to implement the page display method applied to the server according to the foregoing embodiment. Each of the clients 820 is configured to implement the page display method applied to the client provided in the foregoing embodiment.

In the page display system in the embodiment of the invention, the server determines the target page template corresponding to the target page display request according to the current client type and the target page identifier in the target page display request sent by the current client and the mapping information of the pre-configured type page template, determines the target data filling mode corresponding to the target page component in the target page template based on the target page component identifier in the target page template and the mapping relation between the pre-configured page component identifier and the preset data filling mode, fills the data in the target page component based on the target data filling mode, sends the target page component after the data filling to the current client, and renders the data based on the target page component after the data filling by the current client and displays the rendered target page, so that the unified display of the page can be performed for different types of clients by utilizing the pre-configured page template mapping information and the mapping relation between the page component identifier and the preset data filling mode, the multiplexing and the configurability of the page display logic can be realized, and the effect of one-end development and multi-end application can be achieved, thereby reducing the development workload and improving the development efficiency and the flexibility.

Fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. FIG. 9 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.

As shown in fig. 9, electronic device 12 is embodied in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Electronic device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 9, and commonly referred to as a "hard drive"). Although not shown in FIG. 9, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.

Electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with electronic device 12, and/or with any devices (e.g., network card, modem, etc.) that enable electronic device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via the network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 via the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, implementing a page display method provided by the present embodiment.

Of course, those skilled in the art can understand that the processor can also implement the technical solution of the page display method provided by any embodiment of the present invention.

The present embodiment provides a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements the page presentation method as provided by any of the embodiments of the present invention.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer-readable storage medium may be, for example but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, 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 the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It will be understood by those skilled in the art that the modules or steps of the invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and optionally they may be implemented by program code executable by a computing device, such that it may be stored in a memory device and executed by a computing device, or it may be separately fabricated into various integrated circuit modules, or it may be fabricated by fabricating a plurality of modules or steps thereof into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

It is to be noted that the foregoing description is only exemplary of the invention and that the principles of the technology may be employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A page display method is applied to a server and comprises the following steps:

determining a target page template corresponding to the target page display request based on the current client type, the target page identifier and preset type page template mapping information;

and based on the target data filling mode, performing data filling on the target page component, and sending the target page component after data filling to the current client, so that the current client performs data rendering based on the target page component after data filling, and displays a rendered target page.

2. The method according to claim 1, wherein the determining a target page template corresponding to the target page display request based on the current client type, the target page identifier and preconfigured type page template mapping information comprises:

determining target page template mapping information corresponding to the current client type based on the current client type and a mapping relation between a preset client type and preset page template mapping information;

and determining a target page template corresponding to the target page display request based on the target page identifier and the mapping relation between the page identifier in the target page template mapping information and a preset page template.

3. The method of claim 1, wherein the target page show request further comprises a current business state;

the determining a target page template corresponding to the target page display request based on the current client type, the target page identifier and pre-configured type page template mapping information includes:

and determining a target page template corresponding to the target page display request based on the current client type, the target page identifier, the current service state and preset type state page template mapping information.

4. The method according to claim 3, wherein the determining a target page template corresponding to the target page display request based on the current client type, the target page identifier, the current business state, and pre-configured type state page template mapping information comprises:

determining target state page template mapping information corresponding to the current client type based on the current client type and a mapping relation between a pre-configured client type and preset state page template mapping information;

determining target state template mapping information corresponding to the target page identifier based on the target page identifier and a mapping relation between the page identifier in the target state page template mapping information and preset state template mapping information;

and determining a target page template corresponding to the target page display request based on the current business state and the mapping relation between the business state in the target state template mapping information and a preset page template.

5. The method of claim 1, wherein the data-populating the target page component based on the target data-population manner includes:

and performing data filling on the target page component by calling a data filling function in the target data filling implementation class corresponding to the target data filling mode.

6. The method of claim 1, further comprising:

determining a data filling implementation class based on a preset text file corresponding to a data filling interface by calling an implementation class query function, wherein the file name of the preset text file is a fully-limited name of the data filling interface, and the fully-limited name of the data filling implementation class is stored in the preset text file;

and rewriting the data filling function in the data filling implementation class by calling a rewriting interface.

7. The method according to claim 1, wherein the sending the data-filled target page component to the current client, so that the current client performs data rendering based on the data-filled target page component and displays a rendered target page, comprises:

acquiring target page style information corresponding to the target page template;

and sending the target page component and the target page style information after data filling to the current client so as to enable the current client to perform data rendering based on the target page component and the target page style information after data filling, and displaying the rendered target page.

8. A page display method is applied to a client side and comprises the following steps:

9. The method of claim 8, wherein the rendering of data based on the target page components populated with data sent by the server comprises:

if the static data identification information exists in the target page component which is filled with the data and sent by the server, generating a static data acquisition request based on the static data identification information, and sending the static data acquisition request to a distributed server;

and acquiring the static data returned by the distributed server based on the static data acquisition request.

10. The method of claim 8, further comprising:

receiving target page style information corresponding to the target page template sent by the server;

the data rendering based on the target page assembly filled with the data sent by the server comprises the following steps:

and performing data rendering based on the target page component and the target page style information which are filled with the data sent by the server.

11. The method of claim 10, wherein the data rendering based on the target page components and the target page style information filled with data sent by the server comprises:

comparing the original page style information corresponding to the current client with the target page style information;

and if the original page style information is inconsistent with the target page style information, performing data division and integration on a target page component filled with data sent by the server based on the inconsistent page style to obtain a target page component corresponding to the original page style information, and performing data rendering on the target page component corresponding to the original page style information.

12. A page display apparatus, integrated into a server, comprising:

13. A page display device, integrated in a client, comprising:

and the data rendering module is used for performing data rendering on the target page assembly filled with the data sent by the server and displaying the rendered target page.

14. A page presentation system, the system comprising: a server and different types of clients;

wherein, the server is used for realizing the page display method of any one of claims 1 to 7;

each of the clients is configured to implement the page display method of any one of claims 8 to 11.

15. An electronic device, characterized in that the electronic device comprises:

one or more processors;

a memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the page presentation method of any of claims 1-11.

16. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the page presentation method according to any one of claims 1 to 11.