CN111797345B - Application page display method, device, computer equipment and storage medium - Google Patents
Application page display method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111797345B CN111797345B CN201910277120.9A CN201910277120A CN111797345B CN 111797345 B CN111797345 B CN 111797345B CN 201910277120 A CN201910277120 A CN 201910277120A CN 111797345 B CN111797345 B CN 111797345B
- Authority
- CN
- China
- Prior art keywords
- page
- identifier
- client
- displayed
- type
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000004590 computer program Methods 0.000 claims description 9
- 238000009877 rendering Methods 0.000 claims 2
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 6
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000003491 array Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000004069 differentiation Effects 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
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, the identifier of the first page and the client type identifier corresponding to the identifier of the first page are sent to a preset plug-in, so that the preset plug-in 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; and acquiring the first page to be displayed according to the header data in the service request of the first page. Therefore, the purpose of truly displaying the type pages of each terminal 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 an application page display method, an application page display device, 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, while a PC-side type page is displayed in the PC-side, a mobile-side page is displayed, and at present, a smaller container width is mainly set on the mobile-side page, and the mobile-side page is requested in the PC-side container, so that the returned mobile-side page is not a real mobile-side page.
As can be seen, in the related art, in one type of terminal, the page of the other type of terminal cannot be actually displayed while the page of the one type of terminal is displayed.
Disclosure of Invention
The application provides an application page display method which is used for solving the problem of how to truly include pages in different types of terminals in one large page.
In one aspect, an embodiment 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, the identifier of the first page and the client type identifier corresponding to the identifier of the first page are sent to a preset plug-in, so that the preset plug-in 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;
and acquiring the first page to be displayed according to the header 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 header 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 header 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 device, including:
The first acquisition module is used for 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;
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 identification of the first page and the client type identification corresponding to the identification of the first page to a preset plug-in unit when the client type identification corresponding to the identification of the first page is not matched with the type identification of the first client, so that the preset plug-in unit modifies head data in a service request of the first page according to the client type identification corresponding to the identification of the first page;
And the third acquisition module is used for acquiring the first page to be displayed according to the header data in the service request of the first page.
When the client type corresponding to the page to be displayed is not matched with the client type initiating the service request, the application page display device modifies the header data of the page to be displayed through the plug-in, and acquires the real page to be displayed according to the modified header data, so that the purpose of really displaying the page of each terminal type in a certain type of terminal is realized.
Another embodiment of the present application provides a computer device, including a processor and a memory;
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 the embodiment of the aspect.
Another embodiment of the present application proposes a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements an application page presentation method as described in the embodiment of the above aspect.
Another aspect of the present application provides a computer program product comprising a computer program which, when executed by a processor, implements an application page presentation method according to an embodiment of the above aspect.
Additional aspects and advantages of the 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 application.
Drawings
The foregoing and/or additional aspects and advantages of the application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
Fig. 1 is a flow chart of an application page display method according to an embodiment of the present application;
fig. 2 is a flow chart 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-side browser according to an embodiment of the present application;
Fig. 4 is a schematic structural diagram of an application page display device 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
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative and intended to explain the present application and should not be construed as limiting the application.
Application page presentation methods, apparatuses, computer devices, and storage media according to embodiments of the present application are described below with reference to the accompanying drawings.
Fig. 1 is a flow chart of an application page display method according to an embodiment of the present application.
The application page display method provided by the embodiment of the application can be applied to a browser, and the purpose of really displaying pages in different types of terminals in the pages of the browser application is realized.
As shown in fig. 1, the application page presentation method includes:
step 101, a service request sent by a first client is obtained, wherein the service request comprises a type identifier and a user identifier of the first client.
In this embodiment, the first client may be an application running on a browser, for example, a hundred statistics application. When a user initiates a service request in a first client page, a browser acquires the service request sent by the first client. The service request sent by the first client comprises a type identifier and a 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 may be a user account of a user login client, etc.
Taking hundred-degree statistics application as an example, the hundred-degree statistics application is a browser application, and can count and analyze user behaviors of the current website or application, and display analysis results in a browser page. For example, when a user clicks on a thermodynamic diagram in a hundred-degree statistical application in a PC-side browser, the browser obtains a service request for viewing the thermodynamic diagram, where the service request includes information of a type identifier PC-side and a user account of the hundred-degree statistical application.
Step 102, obtaining 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 in the first client, and then the browser can acquire the identification of each page to be displayed corresponding to the user identification according to the configuration information corresponding to the user identification. The configuration information may be data information to be counted, which is set by a user.
For example, the user sets the use conditions of checking the click quantity, the number of users, and the like of a certain website on the PC end and the mobile end, and then the browser can acquire the page identifications of the website pages on different terminals.
And step 103, determining a client type identifier corresponding to the identifier of each page to be displayed according to a preset rule.
In practical applications, when multiple pages are displayed in a browser page, multiple page types to be displayed may be different, for example, the page to be displayed in the browser includes 1 PC side page and 1 mobile side page. Therefore, in this embodiment, it is necessary to determine the client type identifier corresponding to the identifier of each page to be displayed.
In this embodiment, a preset rule may be used to determine a client type identifier corresponding to each page identifier to be displayed.
As a possible implementation manner, the browser may determine, according to configuration information corresponding to the user identifier, a client type identifier corresponding to the identifier of each page to be displayed.
For example, the user may set data to be counted, for example, the use condition of the application a on the mobile terminal and the use condition on the PC terminal, such as the click rate, the number of users, the use time period, and the like, and then it may be determined that the pages to be displayed are two, and the two pages to be displayed are a mobile terminal type page and a PC terminal 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 page a and page B, the page a counts the use condition of the application B at the mobile terminal, 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, the data source of the page B is PC terminal data, then the page a can be determined to be a mobile terminal type page, and the page B is a PC terminal type page.
Or the browser can also determine the client type of the page to be displayed of each page according to the client type corresponding to the version of the application or the website to be counted. For example, some applications may only have a mobile version and only run on the mobile terminal, or some applications may only have a PC version and only run on the PC terminal, or both the mobile terminal and the PC terminal may be able to determine a client type corresponding to a type identifier of a page to be displayed according to a client type corresponding to a version of an application to be viewed.
Step 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, the identifier of the first page and the client type identifier corresponding to the identifier of the first page are sent to a preset plugin, so that the preset plugin modifies 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 a to-be-displayed page whose client type identifier corresponding to the identifier is not matched with the type identifier of the first client, the to-be-displayed page is referred to as a first page.
In this embodiment, a client type identifier corresponding to an identifier of each page to be displayed is compared with a type identifier of the first client.
Because each page to be displayed has a corresponding service request, the corresponding display page can be acquired 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 plug-in.
The preset plugin modifies 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 specifically modifies a server in the header data in the service request of the first page into a 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 module may modify a server in header data in a service request of the first page from a server corresponding to the PC 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, and then the plug-in may modify a server side in the header data in the first page service request from a server side corresponding to the mobile terminal to a server side corresponding to the PC terminal.
Step 105, obtaining the first page to be displayed according to the header 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 the server corresponding to the header data in the service request of the first page, which is referred to herein as the first server. 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 header 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 header data, so that the purpose of really displaying the page of each terminal type in a certain type of terminal is achieved.
The above embodiment describes the 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 initiates the service request, and the case when the two are matched is described below by the method shown in fig. 2. Fig. 2 is a 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:
Step 201, a service request sent by a first client is obtained, where the service request includes a type identifier and a user identifier of the first client.
Step 202, obtaining the identification of each page to be displayed corresponding to the user identification.
Step 203, determining a client type identifier corresponding to the identifier of each page to be displayed according to a preset rule.
Step 204, if the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, the identifier of the first page and the client type identifier corresponding to the identifier of the first page are sent to a preset plugin, so that the preset plugin modifies header data in the service request of the first page according to the client type identifier corresponding to the identifier of the first page.
Step 205, obtaining the first page to be displayed according to the header data in the service request of the first page.
In this embodiment, steps 201 to 205 are similar to steps 101 to 105 described above, and thus are not repeated here.
Step 206, if the client type identifier corresponding to the identifier of the second page matches 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 obtain the second page.
In this embodiment, in order to facilitate differentiation, the to-be-displayed page whose identifier corresponds to the client type and the type identifier of the first client is matched is referred to as a second page.
In this embodiment, the type of the client corresponding to the identifier of each page to be displayed is compared with the type identifier of the first client. And when the type of the client 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, 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.
The type of the client 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 page request may be directly sent to the server corresponding to the second page, i.e. the server matched with the PC. For another example, the mobile client initiates the service request, and the second page to be displayed is the mobile terminal page, so that the page request can be directly sent to the service terminal corresponding to the mobile terminal page, that is, the service terminal matched with the mobile terminal.
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 header data of the first page is modified through the plug-in, the first page is obtained according to the modified header 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 corresponding to the page to be displayed, so that all terminal type pages can be displayed in the browser page at the same time.
The application page display method of the embodiment of the application is described below by taking a service request initiated by a PC client as an example. Fig. 3 is a schematic diagram of a process of acquiring a page to be displayed by a PC-side browser according to an embodiment of the present application.
In fig. 3, the user accesses the website in the PC-side browser, where 3 different pages are to be viewed simultaneously, i.e. 2 PC pages and 1 moving page are to be displayed simultaneously in the browser, i.e. PC page 1, PC page 2 and moving page 3 are to be viewed simultaneously.
The browser judges that the client type corresponding to the mobile page 3 is not a PC terminal but a mobile terminal, and sends a message that the mobile page 3 is of the mobile terminal type to the browser plug-in through postMessage or other modes. The browser plug-in modifies the service end in the header data in the service request of the mobile page into the service end with the type of the mobile end corresponding to the mobile page 3, and sends the modified header data to the PC browser. The PC browser sends a page request to a server corresponding to the header data in the mobile page 3 service request to acquire the mobile page 3, and for the PC page 1 and the PC page 2, the PC browser directly sends the page request to the server matched with the PC terminal to acquire the PC page 1 and the PC page 2.
Therefore, when the mobile terminal page is viewed in the PC terminal browser, the head data in the page request of the mobile page can be modified through the plug-in when the mobile terminal page is requested to the server terminal with the type of the mobile terminal, so that the real server terminal corresponding to the mobile page is requested, and the scene of mixedly viewing the PC page and the mobile page on the PC terminal browser is achieved.
In order to achieve the above embodiment, the embodiment of the present application further provides an application page display device. Fig. 4 is a schematic structural diagram of an application page display device according to an embodiment of the present application.
As shown in fig. 4, the application page presentation apparatus includes: a first acquisition module 410, a second acquisition module 420, a determination module 430, a first transmission module 440, and a third acquisition 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 page to be displayed corresponding to the user identifier;
The determining module 430 is configured to determine, according to a preset rule, a client type identifier corresponding to an identifier of each page to be displayed;
The first sending module 440 is configured to send 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 header data in a service request of the first page according to the client type identifier corresponding to the identifier of the first page;
and 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 one 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 one 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 alternatively
And determining a client type identifier corresponding to the identifier of each page to be displayed according to the data source constituting each page to be displayed.
In one 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 so as to acquire the first page.
In one 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 type identifier of the client corresponding to the identifier of the second page is matched with the type identifier of the first client;
The type of the client corresponding to the second server is matched with the type of the first client.
It should be noted that the explanation of the embodiment of the application page display method is also applicable to the application page display device of this embodiment, so that the explanation is omitted here.
When the client type corresponding to the page to be displayed is not matched with the client type initiating the service request, the application page display device modifies the header data of the page to be displayed through the plug-in, and acquires the real page to be displayed according to the modified header data, so that the purpose of really displaying the page of each terminal type in a certain type of terminal is realized.
In order to implement the above embodiments, the embodiments of the present application further provide a computer device, including a processor and a memory;
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 the above 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 merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present application.
As shown in FIG. 5, the computer device 12 is in the form of a general purpose computing device. Components of computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.
Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include industry Standard architecture (Industry Standard Architecture; hereinafter ISA) bus, micro channel architecture (Micro Channel Architecture; hereinafter MAC) bus, enhanced ISA bus, video electronics standards Association (Video Electronics Standards Association; hereinafter VESA) local bus, and peripheral component interconnect (PERIPHERAL COMPONENT INTERCONNECTION; hereinafter PCI) bus.
Computer device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter: RAM) 30 and/or cache memory 32. The computer 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 or write to non-removable, nonvolatile magnetic media (not shown in FIG. 5, commonly referred to as a "hard disk drive"). Although not shown in fig. 5, a 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 compact disk read only memory (Compact Disc Read Only Memory; hereinafter CD-ROM), digital versatile read only optical disk (Digital Video Disc Read Only Memory; hereinafter DVD-ROM), or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of embodiments of the application.
A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, 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 or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.
The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the computer device 12, and/or any devices (e.g., network card, modem, etc.) that enable the computer device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Moreover, the computer device 12 may also communicate with one or more networks such as a local area network (Local Area Network; hereinafter: LAN), a wide area network (Wide Area Network; hereinafter: WAN) and/or a public network such as the Internet via the network adapter 20. As shown, network adapter 20 communicates with other modules of computer device 12 via bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with computer device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing the methods mentioned in the foregoing embodiments.
In order to achieve the above embodiments, the embodiments of the present application further provide a computer-readable storage medium having stored thereon a computer program that, when executed by a processor, implements the application page presentation method as described in the above embodiments.
In order to achieve the above embodiments, the embodiments of the present application further provide a computer program product, including a computer program, which when executed by a processor, implements the application page presentation method according to the above embodiments.
In the description of this specification, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "plurality" means at least two, for example, two, three, etc., unless specifically defined 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 specific logical functions or steps of the process, and additional 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 from that shown or discussed, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing 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). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may 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 is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. As with the other embodiments, if implemented in hardware, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like. While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.
Claims (11)
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; the determining, according to a preset rule, a client type identifier corresponding to an 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 determining a client type identifier corresponding to the identifier of each page to be displayed according to the data source forming each page to be displayed;
If the client type identifier corresponding to the identifier of the first page is not matched with the type identifier of the first client, the identifier of the first page and the client type identifier corresponding to the identifier of the first page are sent to a preset plug-in, so that the preset plug-in modifies the server side in the header data in the service request of the first page into the server side corresponding to the client type corresponding to the identifier of the first page;
and acquiring the first page to be displayed according to the header data in the service request of the first page.
2. The method of claim 1, wherein the obtaining the identity of each page to be displayed corresponding to the user identity 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 of claim 1, wherein the obtaining the first page to be presented according to the header data in the service request of the first page comprises:
And sending a first page request to a first service end corresponding to the head data in the service request of the first page so as to acquire the first page.
4. A method according to any one of claims 1 to 3, 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, a second page request is sent to a second server corresponding to the identifier of the second page to acquire the second page;
the type of the client corresponding to the second server is matched with the type of the first client.
5. An application page presentation apparatus, comprising:
The first acquisition module is used for 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;
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 determining, according to a preset rule, a client type identifier corresponding to an 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 determining a client type identifier corresponding to the identifier of each page to be displayed according to the data source forming each page to be displayed;
The first sending module is used for sending the identification of the first page and the client type identification corresponding to the identification of the first page to a preset plug-in unit when the client type identification corresponding to the identification of the first page is not matched with the type identification of the first client, so that the preset plug-in unit can modify the server side in the header data of the service request of the first page into the server side corresponding to the client type corresponding to the identification of the first page;
And the third acquisition module is used for acquiring the first page to be displayed according to the header data in the service request of the first page.
6. The apparatus of claim 5, wherein the second acquisition 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.
7. The apparatus of claim 5, wherein the third acquisition module is specifically configured to:
And sending a first page request to a first service end corresponding to the head data in the service request of the first page so as to acquire the first page.
8. The apparatus of any one of claims 5-7, 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 type identifier of the client corresponding to the identifier of the second page is matched with the type identifier of the first client;
the type of the client corresponding to the second server is matched with the type of the first client.
9. A computer device comprising a processor and a memory;
Wherein the processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory for implementing the application page presentation method according to any one of claims 1 to 4.
10. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the application page rendering method of any of claims 1-4.
11. A computer program product comprising a computer program which, when executed by a processor, implements the application page rendering method according to any one of claims 1-4.
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 CN111797345A (en) | 2020-10-20 |
| CN111797345B true 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) |
Families Citing this family (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 |
|---|
| Characterizing HTTP Traffic of Mobile Internet Services in Provincial Network;Pengcheng Jiang等;2014 Sixth International Conference on Intelligent Human-Machine Systems and Cybernetics;20141009;全文 * |
| 有效的爬行Ajax页面的网络爬行算法;李华波;吴礼发;赖海光;郑成辉;黄康宇;;电子科技大学学报;20130130(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111797345A (en) | 2020-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110825456B (en) | Loading time calculation method, loading time calculation device, computer equipment and storage medium | |
| CN110674025B (en) | Interactive behavior monitoring method and device and computer equipment | |
| CN108959430B (en) | Advertisement promotion data acquisition method, device and equipment | |
| CN111797345B (en) | Application page display method, device, computer equipment and storage medium | |
| CN112000911B (en) | Page management method, device, electronic equipment and storage medium | |
| CN112069425A (en) | Log management method and device, electronic equipment and readable storage medium | |
| CN112711398A (en) | Method, device and equipment for generating buried point file and storage medium | |
| CN110110236B (en) | Information pushing method, device, equipment and storage medium | |
| CN109495549A (en) | Method, equipment and the computer storage medium of work are drawn in a kind of application | |
| CN114461691A (en) | Control method and device of state machine, electronic equipment and storage medium | |
| CN113312036B (en) | Large screen display method, device and equipment of Web page and storage medium | |
| CN112685672B (en) | Page session behavior trace backtracking method and device and electronic equipment | |
| CN115225347B (en) | Method and device for monitoring target range resources | |
| CN109740094A (en) | Page monitoring method, equipment and computer storage medium | |
| CN111158829A (en) | Operation rollback processing method and device | |
| CN112994900B (en) | File countersigning method, device, client, server and storage medium | |
| CN112135199B (en) | Video playing method based on multiple types of video sources and related equipment | |
| CN113923190B (en) | Equipment identification jump identification method and device, server and storage medium | |
| CN114639056A (en) | Live content identification method and device, computer equipment and storage medium | |
| CN111741046B (en) | Data reporting method, data acquisition method, device, equipment and medium | |
| CN114218000A (en) | Log management method and device, electronic equipment and computer readable storage medium | |
| CN109348236B (en) | Storage capacity evaluation method and device, server and storage medium | |
| CN112288452B (en) | Advertisement previewing method and device, electronic equipment and storage medium | |
| CN113420042A (en) | Data statistics method, device, equipment and storage medium based on presentation | |
| CN110598199B (en) | Data stream processing method, device, computer equipment and storage medium |
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 |