CN111797345A - Application page display method and device, computer equipment and storage medium - Google Patents
Application page display method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111797345A CN111797345A CN201910277120.9A CN201910277120A CN111797345A CN 111797345 A CN111797345 A CN 111797345A CN 201910277120 A CN201910277120 A CN 201910277120A CN 111797345 A CN111797345 A CN 111797345A
- Authority
- CN
- China
- Prior art keywords
- page
- identifier
- client
- displayed
- service request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000004590 computer program Methods 0.000 claims description 5
- 238000009877 rendering Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 5
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application provides an application page display method, an application page display device, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring a service request sent by a first client, wherein the service request comprises a type identifier and a user identifier of the first client; acquiring the identification of each page to be displayed corresponding to the user identification; determining a client type identifier corresponding to the identifier of each page to be displayed according to a preset rule; if the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, sending the identifier of the first page and the client type identifier corresponding to the identifier of the first page to a preset plugin, so that the preset plugin modifies the header data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page; and acquiring the first page to be displayed according to the head data in the service request of the first page. Therefore, the purpose of really showing the page of each terminal type in a certain type of terminal is achieved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for displaying an application page, a computer device, and a storage medium.
Background
In practical applications, there may be a need to present multiple terminal type pages in a browser application. For example, when a PC-side page is displayed and a mobile-side page is displayed at the same time, a smaller container width is mainly set in the mobile-side page at present, and the mobile-side page is requested in the PC-side container, so that the returned page is not a real mobile-side page.
Therefore, in the related art, the pages of the terminal of the type cannot be displayed in one type of terminal, and the pages of the terminals of other types cannot be really displayed at the same time.
Disclosure of Invention
The application provides an application page display method, which is used for solving the problem of how to really include pages in different types of terminals in one large page.
An embodiment of one aspect of the present application provides an application page display method, including:
acquiring a service request sent by a first client, wherein the service request comprises a type identifier and a user identifier of the first client;
acquiring the identification of each page to be displayed corresponding to the user identification;
determining a client type identifier corresponding to the identifier of each page to be displayed according to a preset rule;
if the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, sending the identifier of the first page and the client type identifier corresponding to the identifier of the first page to a preset plugin, so that the preset plugin modifies the header data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page;
and acquiring the first page to be displayed according to the head data in the service request of the first page.
According to the application page display method, when the client type corresponding to the page to be displayed is not matched with the client type initiating the service request, the head data of the page to be displayed is modified through the plug-in, and the real page to be displayed is obtained according to the modified head data, so that the purpose of really displaying the page of each terminal type in a certain type of terminal is achieved.
Another embodiment of the present application provides an application page display apparatus, including:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a service request sent by a first client, and the service request comprises a type identifier and a user identifier of the first client;
the second acquisition module is used for acquiring the identification of each page to be displayed corresponding to the user identification;
the determining module is used for determining a client type identifier corresponding to the identifier of each page to be displayed according to a preset rule;
the first sending module is used for sending the identifier of the first page and the client type identifier corresponding to the identifier of the first page to a preset plugin when the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, so that the preset plugin modifies the header data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page;
and the third acquisition module is used for acquiring the first page to be displayed according to the head data in the service request of the first page.
According to the application page display device, when the client type corresponding to the page to be displayed is not matched with the client type initiating the service request, the head data of the page to be displayed is modified through the plug-in, and the real page to be displayed is obtained according to the modified head data, so that the purpose of really displaying the page of each terminal type in a certain type of terminal is achieved.
Another embodiment of the present application provides a computer device, including a processor and a memory;
the processor reads the executable program code stored in the memory to run a program corresponding to the executable program code, so as to implement the application page presentation method according to the embodiment of the aspect.
Another embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the application page displaying method according to the above embodiment of the aspect.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic flowchart of an application page display method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of another application page display method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a process of acquiring a page to be displayed by a PC browser according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an application page presentation apparatus according to an embodiment of the present application;
FIG. 5 illustrates a block diagram of an exemplary computer device suitable for use in implementing embodiments of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.
An application page presentation method, an apparatus, a computer device, and a storage medium according to embodiments of the present application are described below with reference to the accompanying drawings.
Fig. 1 is a schematic flowchart of an application page display method according to an embodiment of the present application.
The application page display method can be applied to the browser, and achieves the purpose of really displaying the pages including the pages in different types of terminals in the page applied by the browser.
As shown in fig. 1, the application page display method includes:
In this embodiment, the first client may be an application running on a browser, for example, a hundredth statistics application. When a user initiates a service request in a first client page, the browser acquires the service request sent by the first client. The service request sent by the first client includes the type identifier and the user identifier of the first client.
The type identifier of the first client is used for representing the type of the first client, and the first client can be a PC client or a mobile client; the user identification can be a user account of the user logging in the client and the like.
Taking the hundredth statistic application as an example, the hundredth statistic application is a browser application, and can count and analyze user behaviors of a current website or application and display an analysis result in a browser page. For example, when a user clicks a thermodynamic diagram in a centesimal statistic application in a browser of a PC (personal computer), the browser acquires a service request for viewing the thermodynamic diagram, wherein the service request comprises type identification PC (personal computer) end and user account information of the centesimal statistic application.
And 102, acquiring the identification of each page to be displayed corresponding to the user identification.
After the user logs in the first client, configuration information can be set at the first client, and then the browser can acquire the identifier of each to-be-displayed page corresponding to the user identifier according to the configuration information corresponding to the user identifier. The configuration information may be data information to be counted set by a user.
For example, if the user sets the usage such as the click rate and the number of users of a website on the PC side and the mobile side, the browser may obtain the page identifiers of the website pages at different terminals.
In practical applications, when multiple pages are displayed in a browser page, the types of the multiple pages to be displayed may be different, for example, the pages to be displayed in the browser include 1 PC end page and 1 mobile end page. Therefore, in this embodiment, the client type identifier corresponding to the identifier of each page to be displayed needs to be determined.
In this embodiment, a preset rule may be used to determine the client type identifier corresponding to each to-be-displayed page identifier.
As a possible implementation manner, the browser may determine, according to the configuration information corresponding to the user identifier, a client type identifier corresponding to an identifier of each page to be displayed.
For example, the user may set data to be counted, for example, the usage of the application a on the mobile side and the usage on the PC side, such as the click rate, the number of people using, the usage time, and the like, and then it may be determined that there are two pages to be displayed, and the two pages to be displayed are a mobile side type page and a PC side type page.
As another possible implementation manner, the client type identifier corresponding to the identifier of each page to be displayed may be determined according to the data source constituting each page to be displayed.
For example, the pages to be displayed are a page a and a page B, the page a counts the use condition of the application B at the mobile terminal, and the page B counts the use condition of the application B at the PC terminal, that is, the data source of the page a is mobile terminal data, and the data source of the page B is PC terminal data, so that it can be determined that the page a is a mobile terminal type page and the page B is a PC terminal type page.
Or, the browser may also determine the client type of the page to be displayed of each page according to the client type corresponding to the version to which the application or the website to be counted belongs. For example, some applications may only have a mobile version and only can be run on a mobile terminal, or some applications may only have a PC version and only can be run on a PC terminal, or both the mobile terminal and the PC terminal may be used, and then the client type corresponding to the type identifier of the page to be displayed may be determined according to the client type corresponding to the version of the application to be viewed.
And 104, if the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, sending the identifier of the first page and the client type identifier corresponding to the identifier of the first page to a preset plug-in, so that the preset plug-in modifies the header data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page.
In this embodiment, in order to facilitate distinguishing the page to be displayed whose client type identifier corresponding to the identifier of the page to be displayed is not matched with the type identifier of the first client, the page to be displayed is referred to as a first page.
In this embodiment, the client type identifier corresponding to the identifier of each page to be displayed is compared with the type identifier of the first client.
Because each page to be displayed has a corresponding service request, the corresponding display page can be obtained from the corresponding server according to the service request of the page to be displayed. In this embodiment, when the client type identifier corresponding to the identifier of the first page is not matched with the first client type identifier, the identifier of the first page and the client type corresponding to the identifier of the first page are sent to a preset plugin.
The preset plug-in modifies the head data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page, and specifically modifies the server in the head data in the service request of the first page to the server corresponding to the client type corresponding to the identifier of the first page.
For example, the first page is a mobile terminal type page, the first client is a PC client, and the plug-in may modify a server in header data in the service request of the first page from a server corresponding to the PC terminal to a server corresponding to the mobile terminal.
For another example, the first page is a PC-side type page, and the first client is a mobile client, so that the plug-in may modify the server in the header data in the first page service request from the server corresponding to the mobile terminal to the server corresponding to the PC-side.
And 105, acquiring the first page to be displayed according to the head data in the service request of the first page.
In this embodiment, the header data in the page service request includes server information, and then the first page request may be sent to a server corresponding to the header data in the service request of the first page, which is referred to as a first server herein. And the first server sends the first page to the browser according to the first page request. Therefore, the browser can acquire the real first page from the server corresponding to the type identifier corresponding to the identifier of the first page.
According to the application page display method, when the client type corresponding to the page to be displayed is not matched with the client type initiating the service request, the head data of the page to be displayed is modified through the plug-in, and the real page to be displayed is obtained according to the modified head data, so that the purpose that the page of each terminal type is really displayed in a certain type of terminal is achieved.
The above embodiment describes a case when the client type identifier corresponding to the identifier of the page to be displayed does not match the type identifier of the first client that initiated the service request, and a case when the client type identifier and the type identifier match is described below by a method shown in fig. 2. Fig. 2 is a schematic flowchart of another application page display method according to an embodiment of the present application.
As shown in fig. 2, the application page display method includes:
In this embodiment, steps 201 to 205 are similar to steps 101 to 105, and thus are not described herein again.
In step 206, if the client type identifier corresponding to the identifier of the second page matches the type identifier of the first client, a second page request is sent to a second server corresponding to the identifier of the second page, so as to obtain the second page.
In this embodiment, for convenience of distinguishing, the page to be displayed, in which the client type corresponding to the identifier of the page to be displayed is matched with the type identifier of the first client, is referred to as a second page.
In this embodiment, the client type corresponding to the identifier of each page to be displayed is compared with the type identifier of the first client. And when the client type corresponding to the identifier of the second page is matched with the type identifier of the first client, sending a second page request to a second server corresponding to the identifier of the second page, specifically, sending the second page request to a second server corresponding to the header data in the service request of the second page, and returning the second page by the second server according to the second page request.
That is to say, when the client type corresponding to the second page matches the client type of the first client, the page request is directly sent to the server corresponding to the second page, and the second page is obtained.
And the client type corresponding to the second server is matched with the type of the first client.
For example, if the second page to be displayed is a PC page, the service request initiated by the PC client may directly send a page request to a server corresponding to the second page, that is, a server matched with the PC. For another example, if the second page to be displayed is a mobile-end page in the service request initiated by the mobile client, the page request may be directly sent to a server corresponding to the mobile-end page, that is, a server matched with the mobile end.
According to the application page display method, the client type corresponding to the identification of each page to be displayed is compared with the type of the first client, when the client type identification corresponding to the identification of the page to be displayed is not matched with the type identification of the first client, the head data of the first page is modified through the plug-in, the first page is obtained according to the modified head data, and when the client type corresponding to the identification of the page to be displayed is matched with the type identification of the first client, the client type corresponding to the identification of the page to be displayed is directly obtained from the server side corresponding to the page to be displayed, so that each terminal type page can be truly displayed in the browser page at the same time.
The application page display method according to the embodiment of the present application is described below by taking an example where a PC client initiates a service request. Fig. 3 is a schematic diagram of a process of acquiring a page to be displayed by a PC browser according to an embodiment of the present application.
In fig. 3, a user accesses a website in a PC browser, where 3 different pages are to be viewed at the same time, that is, 2 PC pages and 1 mobile page are to be displayed at the browser, namely, PC page 1(www.baidu.com), PC page 2(a-PC.
The browser determines that the client type corresponding to the mobile page 3 is not a PC (personal computer) terminal but a mobile terminal through judgment, and sends a message that the mobile page 3 is the mobile terminal type to the browser plug-in through a postMessage or in other manners. And the browser plug-in modifies the server in the head data in the service request of the mobile page into the server which is corresponding to the mobile page 3 and is of the type of the mobile end, and sends the modified head data to the PC browser. And for the PC page 1 and the PC page 2, the PC browser directly sends a page request to the server matched with the PC end to obtain the PC page 1 and the PC page 2.
Therefore, when the mobile page is viewed in the PC browser, when a request is made to the server of which the type is the mobile end, the head data in the page request of the mobile page can be modified through the plug-in, so that the server corresponding to the mobile page is really requested, and the purpose of viewing the scenes of the PC page and the mobile page on the PC browser in a mixed manner is achieved.
In order to implement the foregoing embodiment, an application page display device is further provided in the embodiment of the present application. Fig. 4 is a schematic structural diagram of an application page presentation apparatus according to an embodiment of the present application.
As shown in fig. 4, the application page presentation apparatus includes: a first obtaining module 410, a second obtaining module 420, a determining module 430, a first sending module 440, and a third obtaining module 450.
A first obtaining module 410, configured to obtain a service request sent by a first client, where the service request includes a type identifier and a user identifier of the first client;
a second obtaining module 420, configured to obtain an identifier of each to-be-displayed page corresponding to the user identifier;
a determining module 430, configured to determine, according to a preset rule, a client type identifier corresponding to an identifier of each to-be-displayed page;
a first sending module 440, configured to send, when a client type identifier corresponding to an identifier of a first page is not matched with a type identifier of a first client, the identifier of the first page and a client type identifier corresponding to the identifier of the first page to a preset plugin, so that the preset plugin modifies header data in a service request of the first page according to the client type identifier corresponding to the identifier of the first page;
the third obtaining module 450 is configured to obtain the first page to be displayed according to the header data in the service request of the first page.
In a possible implementation manner of the embodiment of the present application, the second obtaining module 420 is specifically configured to:
and acquiring the identification of each page to be displayed corresponding to the user identification according to the configuration information corresponding to the user identification.
In a possible implementation manner of the embodiment of the present application, the determining module 430 is specifically configured to:
determining a client type identifier corresponding to the identifier of each page to be displayed according to the configuration information corresponding to the user identifier;
or,
and determining the client type identifier corresponding to the identifier of each page to be displayed according to the data source forming each page to be displayed.
In a possible implementation manner of the embodiment of the present application, the third obtaining module 450 is specifically configured to:
and sending the first page request to a first service end corresponding to the head data in the service request of the first page to acquire the first page.
In a possible implementation manner of the embodiment of the present application, the apparatus may further include:
the second sending module is used for sending a second page request to a second server corresponding to the identifier of the second page to acquire the second page when the client type identifier corresponding to the identifier of the second page is matched with the type identifier of the first client;
and the client type corresponding to the second server is matched with the type of the first client.
It should be noted that the above explanation of the embodiment of the application page display method is also applicable to the application page display apparatus of the embodiment, and therefore is not repeated herein.
According to the application page display device, when the client type corresponding to the page to be displayed is not matched with the client type initiating the service request, the head data of the page to be displayed is modified through the plug-in, and the real page to be displayed is obtained according to the modified head data, so that the purpose of really displaying the page of each terminal type in a certain type of terminal is achieved.
In order to implement the foregoing embodiments, an embodiment of the present application further provides a computer device, including a processor and a memory;
the processor reads the executable program code stored in the memory to run the program corresponding to the executable program code, so as to implement the application page presentation method according to the embodiment.
FIG. 5 illustrates a block diagram of an exemplary computer device suitable for use in implementing embodiments of the present application. The computer device 12 shown in fig. 5 is only an example and should not bring any limitation to the function and scope of use of the embodiments of the present application.
As shown in FIG. 5, computer device 12 is in the form of a general purpose computing device. The components of computer 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.
Computer device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in 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 perform the functions and/or methodologies of the embodiments described herein.
Computer 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 computer device 12, and/or with any devices (e.g., network card, modem, etc.) that enable computer device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Moreover, computer device 12 may also 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 Network adapter 20. As shown, network adapter 20 communicates with the other modules of computer device 12 via 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 computer 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, for example, implementing the methods mentioned in the foregoing embodiments, by executing programs stored in the system memory 28.
In order to implement the foregoing embodiments, the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the application page display method according to the foregoing embodiments.
In the description of the present specification, the terms "first", "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (12)
1. An application page display method is characterized by comprising the following steps:
acquiring a service request sent by a first client, wherein the service request comprises a type identifier and a user identifier of the first client;
acquiring the identification of each page to be displayed corresponding to the user identification;
determining a client type identifier corresponding to the identifier of each page to be displayed according to a preset rule;
if the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, sending the identifier of the first page and the client type identifier corresponding to the identifier of the first page to a preset plugin, so that the preset plugin modifies the header data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page;
and acquiring the first page to be displayed according to the head data in the service request of the first page.
2. The method of claim 1, wherein the obtaining the identifier of each page to be displayed corresponding to the user identifier comprises:
and acquiring the identification of each page to be displayed corresponding to the user identification according to the configuration information corresponding to the user identification.
3. The method as claimed in claim 1, wherein the determining, according to a preset rule, the client type identifier corresponding to the identifier of each page to be displayed includes:
determining a client type identifier corresponding to the identifier of each page to be displayed according to the configuration information corresponding to the user identifier;
or,
and determining the client type identifier corresponding to the identifier of each page to be displayed according to the data source forming each page to be displayed.
4. The method of claim 1, wherein the obtaining the first page to be rendered according to header data in the service request for the first page comprises:
and sending a first page request to a first service end corresponding to the header data in the service request of the first page to acquire the first page.
5. The method according to any one of claims 1 to 4, wherein after determining the client type identifier corresponding to the identifier of each page to be displayed, the method further comprises:
if the client type identifier corresponding to the identifier of the second page is matched with the type identifier of the first client, sending a second page request to a second server corresponding to the identifier of the second page to acquire the second page;
and the client type corresponding to the second server is matched with the type of the first client.
6. An application page presentation apparatus, comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a service request sent by a first client, and the service request comprises a type identifier and a user identifier of the first client;
the second acquisition module is used for acquiring the identification of each page to be displayed corresponding to the user identification;
the determining module is used for determining a client type identifier corresponding to the identifier of each page to be displayed according to a preset rule;
the first sending module is used for sending the identifier of the first page and the client type identifier corresponding to the identifier of the first page to a preset plugin when the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, so that the preset plugin modifies the header data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page;
and the third acquisition module is used for acquiring the first page to be displayed according to the head data in the service request of the first page.
7. The apparatus of claim 6, wherein the second obtaining module is specifically configured to:
and acquiring the identification of each page to be displayed corresponding to the user identification according to the configuration information corresponding to the user identification.
8. The apparatus of claim 6, wherein the determination module is specifically configured to:
determining a client type identifier corresponding to the identifier of each page to be displayed according to the configuration information corresponding to the user identifier;
or,
and determining the client type identifier corresponding to the identifier of each page to be displayed according to the data source forming each page to be displayed.
9. The apparatus of claim 6, wherein the third obtaining module is specifically configured to:
and sending a first page request to a first service end corresponding to the header data in the service request of the first page to acquire the first page.
10. The apparatus of any of claims 6-9, further comprising:
the second sending module is used for sending a second page request to a second server corresponding to the identifier of the second page to acquire the second page when the client type identifier corresponding to the identifier of the second page is matched with the type identifier of the first client;
and the client type corresponding to the second server is matched with the type of the first client.
11. A computer device comprising a processor and a memory;
wherein the processor executes a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the application page presentation method according to any one of claims 1 to 5.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the application page rendering method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910277120.9A CN111797345B (en) | 2019-04-08 | 2019-04-08 | Application page display method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910277120.9A CN111797345B (en) | 2019-04-08 | 2019-04-08 | Application page display method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111797345A true CN111797345A (en) | 2020-10-20 |
| CN111797345B CN111797345B (en) | 2024-04-30 |
Family
ID=72805541
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910277120.9A Active CN111797345B (en) | 2019-04-08 | 2019-04-08 | Application page display method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111797345B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112684957A (en) * | 2020-12-30 | 2021-04-20 | 上海瑞家信息技术有限公司 | Information display method and device, electronic equipment and medium |
| CN113065061A (en) * | 2021-03-08 | 2021-07-02 | 北京达佳互联信息技术有限公司 | Information display method and device and server |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8595613B1 (en) * | 2012-07-26 | 2013-11-26 | Viasat Inc. | Page element identifier pre-classification for user interface behavior in a communications system |
| CN103491066A (en) * | 2012-06-14 | 2014-01-01 | 腾讯科技（深圳）有限公司 | Method, system, server side equipment and client side equipment for page displaying |
| CN105528452A (en) * | 2015-12-23 | 2016-04-27 | 北京奇虎科技有限公司 | Method and system for loading page data |
| CN108089878A (en) * | 2017-12-14 | 2018-05-29 | 腾讯科技（深圳）有限公司 | Page info shows and generation method, apparatus and system |
-
2019
- 2019-04-08 CN CN201910277120.9A patent/CN111797345B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103491066A (en) * | 2012-06-14 | 2014-01-01 | 腾讯科技（深圳）有限公司 | Method, system, server side equipment and client side equipment for page displaying |
| US8595613B1 (en) * | 2012-07-26 | 2013-11-26 | Viasat Inc. | Page element identifier pre-classification for user interface behavior in a communications system |
| CN105528452A (en) * | 2015-12-23 | 2016-04-27 | 北京奇虎科技有限公司 | Method and system for loading page data |
| CN108089878A (en) * | 2017-12-14 | 2018-05-29 | 腾讯科技（深圳）有限公司 | Page info shows and generation method, apparatus and system |
Non-Patent Citations (2)
| Title |
|---|
| PENGCHENG JIANG等: "Characterizing HTTP Traffic of Mobile Internet Services in Provincial Network", 2014 SIXTH INTERNATIONAL CONFERENCE ON INTELLIGENT HUMAN-MACHINE SYSTEMS AND CYBERNETICS, 9 October 2014 (2014-10-09) * |
| 李华波;吴礼发;赖海光;郑成辉;黄康宇;: "有效的爬行Ajax页面的网络爬行算法", 电子科技大学学报, no. 01, 30 January 2013 (2013-01-30) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112684957A (en) * | 2020-12-30 | 2021-04-20 | 上海瑞家信息技术有限公司 | Information display method and device, electronic equipment and medium |
| CN113065061A (en) * | 2021-03-08 | 2021-07-02 | 北京达佳互联信息技术有限公司 | Information display method and device and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111797345B (en) | 2024-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108959430B (en) | Advertisement promotion data acquisition method, device and equipment | |
| CN108595520B (en) | Method and device for generating multimedia file | |
| CN112000911B (en) | Page management method, device, electronic equipment and storage medium | |
| CN110110236B (en) | Information pushing method, device, equipment and storage medium | |
| CN109960554B (en) | Method, device and computer storage medium for displaying reading content | |
| CN112685672B (en) | Page session behavior trace backtracking method and device and electronic equipment | |
| CN112711398A (en) | Method, device and equipment for generating buried point file and storage medium | |
| CN111797345B (en) | Application page display method, device, computer equipment and storage medium | |
| CN110781063B (en) | Method, device, equipment and storage medium for measuring first screen time of web page | |
| CN113312036B (en) | Large screen display method, device and equipment of Web page and storage medium | |
| CN112994900B (en) | File countersigning method, device, client, server and storage medium | |
| CN109347899B (en) | Method for writing log data in distributed storage system | |
| CN109740094A (en) | Page monitoring method, equipment and computer storage medium | |
| CN111046393B (en) | Vulnerability information uploading method and device, terminal equipment and storage medium | |
| CN108399128A (en) | A kind of generation method of user data, device, server and storage medium | |
| CN109710521B (en) | Multimedia application performance test method and device, computer equipment and storage medium | |
| CN109271543B (en) | Thumbnail display method and device, terminal and computer-readable storage medium | |
| CN115022201B (en) | Data processing function test method, device, equipment and storage medium | |
| CN112035159B (en) | Configuration method, device, equipment and storage medium of audit model | |
| CN115016890A (en) | Virtual machine resource allocation method and device, electronic equipment and storage medium | |
| CN110753136B (en) | Domain name resolution method, device, equipment and storage medium | |
| CN111741046B (en) | Data reporting method, data acquisition method, device, equipment and medium | |
| CN113420042A (en) | Data statistics method, device, equipment and storage medium based on presentation | |
| CN110769027A (en) | Service request processing method and device, computer equipment and storage medium | |
| CN111414470A (en) | Method and device for processing document, computer storage medium and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |