CN113704648A - Page data processing method, device, equipment and storage medium - Google Patents
Page data processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113704648A CN113704648A CN202111011994.3A CN202111011994A CN113704648A CN 113704648 A CN113704648 A CN 113704648A CN 202111011994 A CN202111011994 A CN 202111011994A CN 113704648 A CN113704648 A CN 113704648A
- Authority
- CN
- China
- Prior art keywords
- data
- page
- rendered
- request
- page 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 23
- 238000012545 processing Methods 0.000 claims abstract description 83
- 238000000034 method Methods 0.000 claims abstract description 39
- 230000003068 static effect Effects 0.000 claims description 76
- 230000006870 function Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 13
- 230000004044 response Effects 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 abstract description 4
- 238000013473 artificial intelligence Methods 0.000 abstract description 2
- 238000009877 rendering Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 230000036541 health Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000008571 general function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000000007 visual effect Effects 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/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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
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)
Abstract
The embodiment of the application discloses a page data processing method, a page data processing device, page data processing equipment and a storage medium. The method comprises the following steps: when the first page request is determined to be processed, acquiring first data to be rendered corresponding to the first page request; receiving a second page request, and acquiring second data to be rendered corresponding to the second page request; determining distinguishing data according to the second data to be rendered and the first data to be rendered; and sending the first data to be rendered and the distinguishing data to the target client, so that the target client generates first page data based on the first data to be rendered, and generates second page data based on the first page data and the distinguishing data. Computational resources can be saved. The present application may relate to a blockchain technique, such as the first data to be rendered may be obtained from a blockchain. For example, the first data to be rendered may be acquired based on artificial intelligence techniques. It may also relate to the field of digital medical technology, such as the first page data comprising a medical data file.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing page data.
Background
At present, with the prevalence of terminal devices, more and more Applications (APPs) enter people's lives. In order to meet the increasing business requirements of people, Hybrid mode applications (Hybrid apps) and Web applications (Web apps) have come into force. In Hybrid APPs and Web APPs, the operating system is only a client container of each App, and the business logic in the App is all loaded through a webpage.
In order to obtain page data in a web page, several steps of loading static resource data, loading dynamic interface data and rendering the page are often required. However, the client and the server are coupled, and the page data processing operation may be repeatedly performed, which wastes computing resources.
Disclosure of Invention
The embodiment of the application provides a page data processing method, a page data processing device and a page data processing storage medium, which can avoid repeated execution of page data processing operation and save computing resources.
In a first aspect, an embodiment of the present application provides a page data processing method, where the method includes:
receiving a first page request from a target client, and acquiring first data to be rendered corresponding to the first page request when the first page request is determined to be processed;
receiving a second page request from the target client, and acquiring second data to be rendered corresponding to the second page request;
determining distinguishing data according to the second data to be rendered and the first data to be rendered;
and sending the first data to be rendered and the distinguishing data to the target client so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data.
In a second aspect, an embodiment of the present application further provides another page data processing method, where the method includes:
sending a first page request and a second page request to the target proxy middleware;
receiving first data to be rendered and distinguishing data from the target agent middleware, generating first page data based on the first data to be rendered, and generating second page data based on the first page data and the distinguishing data; the first data to be rendered is first data to be rendered corresponding to the first page request; the difference data is determined by the target agent middleware according to the first data to be rendered and the second data to be rendered, and the second data to be rendered is the second data to be rendered corresponding to the second page request.
In a third aspect, an embodiment of the present application provides a page data processing apparatus, including:
the system comprises an acquisition unit, a processing unit and a display unit, wherein the acquisition unit is used for receiving a first page request from a target client and acquiring first to-be-rendered data corresponding to the first page request when the first page request is determined to be processed;
the obtaining unit is further configured to receive a second page request from the target client, and obtain second data to be rendered corresponding to the second page request;
the determining unit is used for determining distinguishing data according to the second data to be rendered and the first data to be rendered;
and the sending unit is used for sending the first data to be rendered and the distinguishing data to the target client so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data.
In a fourth aspect, an embodiment of the present application further provides another page data processing apparatus, where the page data processing apparatus includes:
the sending unit is used for sending the first page request and the second page request to the target proxy middleware;
the processing unit is used for receiving first data to be rendered and the distinguishing data from the target agent middleware, generating first page data based on the first data to be rendered and generating second page data based on the first page data and the distinguishing data; the first data to be rendered is first data to be rendered corresponding to the first page request; the difference data is determined by the target agent middleware according to the first data to be rendered and the second data to be rendered, and the second data to be rendered is the second data to be rendered corresponding to the second page request.
In a fifth aspect, an embodiment of the present application provides a page data processing apparatus, where the page data processing apparatus includes an input interface and an output interface, and the page data processing apparatus further includes:
a processor adapted to implement one or more instructions; and the number of the first and second groups,
a computer storage medium having stored thereon one or more instructions adapted to be loaded by a processor and to perform the method of the first aspect.
In a sixth aspect, an embodiment of the present application further provides another page data processing device, where the page data processing device includes an input interface and an output interface, and the page data processing device further includes:
a processor adapted to implement one or more instructions; and the number of the first and second groups,
a computer storage medium having stored thereon one or more instructions adapted to be loaded by a processor and to perform the method of the second aspect.
In a seventh aspect, this application further provides a computer-readable storage medium, where computer program instructions are stored, and when executed by a processor, are configured to perform the method of the first aspect; alternatively, the method of the second aspect is performed.
In this embodiment of the present application, the target proxy middleware may receive a first page request from a target client, and when it is determined that the first page request has been processed, obtain first data to be rendered corresponding to the first page request, then receive a second page request from the target client, and obtain second data to be rendered corresponding to the second page request; determining distinguishing data according to the second data to be rendered and the first data to be rendered; and sending the first data to be rendered and the distinguishing data to the target client so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data. When the target agent middleware determines that the first page request is processed, the first data to be rendered corresponding to the first page request can be directly acquired, and the target agent middleware does not need to repeatedly execute the operations of acquiring static resource data, acquiring dynamic interface data and/or assembling the static resource data and the dynamic interface data, so that the computing resources can be saved. In addition, the target agent middleware can also determine the difference data according to the second data to be rendered and the first data to be rendered, so that the target client can generate the second page data based on the first page data and the difference data after generating the first page data, the rendered first page data can be multiplexed, repeated rendering is avoided, and computing resources are saved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a block diagram of a page data processing system according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a page data processing method according to an embodiment of the present application;
FIG. 3 is a schematic flowchart of another page data processing method according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a page data processing apparatus according to an embodiment of the present application;
FIG. 5 is a schematic structural diagram of another page data processing apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a page data processing device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another page data processing device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
At present, with the prevalence of terminal devices, more and more APPs enter people's lives. With the rapid development of scientific technology, in order to meet the increasing business requirements of people, the development mode of an application program is changed, an operating system in terminal equipment is only a client container of various APPs, and business logic in the APPs can be borne through webpages. In order to obtain page data in a web page, several steps of loading static resource data, loading dynamic interface data and rendering the page are often required. In one page data processing scheme, a client can initiate a first resource request to a resource server, the resource server responds to the first resource request to issue static resource data, the client initiates a second resource request to a dynamic interface server after acquiring the static resource data, the dynamic interface server responds to the second resource request to issue dynamic interface data, and the client assembles the static resource data and the dynamic interface data to generate data to be rendered after receiving the static resource data and the dynamic interface data and renders the data to be rendered to obtain page data. The page data processing scheme has a long flow, a long time delay and poor user experience, and a client and a server in the page data processing scheme are coupled, so that static resource data and dynamic interface data can be repeatedly acquired, and computing resources of the client and the server are wasted. In another page data processing scheme, a client may initiate a first page request to a resource server, the resource server responds to the first page request to obtain static resource data and sends the static resource data to a dynamic interface server, and the dynamic interface server obtains dynamic interface data and assembles the static resource data and the dynamic interface data to generate data to be rendered. And the dynamic interface server returns the data to be rendered to the client, so that the client renders the data to be rendered to obtain page data. In the page data processing scheme, the client and the server are coupled, and depending on the server, the server is stressed greatly, static resource data and dynamic interface data can be repeatedly acquired, and computing resources of the client and the server are wasted. The page rendered by the client cannot be reused.
Based on this, the embodiment of the application provides a page data processing method, a page data processing device, page data processing equipment and a storage medium. In the page data processing method, when the first page request is determined to be processed, the target agent middleware can directly acquire the first to-be-rendered data corresponding to the first page request, and the target agent middleware does not need to repeatedly execute the operations of acquiring static resource data, acquiring dynamic interface data and/or assembling the static resource data and the dynamic interface data, so that the computing resources are saved. And the target agent middleware can also receive a second page request from the target client and acquire second data to be rendered corresponding to the second page request. Determining distinguishing data according to the second data to be rendered and the first data to be rendered; and sending the first data to be rendered and the distinguishing data to the target client, so that after the target client generates the first page data based on the first data to be rendered, the target client can generate second page data based on the first page data and the distinguishing data, and the target client can multiplex the rendered first page data, thereby avoiding repeated rendering and saving computing resources.
Referring to fig. 1, fig. 1 shows a schematic architecture diagram of a page data processing system, and as shown in fig. 1, the page data processing system may include a client 11, an agent middleware 12, a resource server 13, and a dynamic interface server 14. The client 11 may be deployed in a terminal device installed with an APP, where the terminal device may be a portable terminal device such as a smart phone, a tablet computer, a wearable terminal device with a wireless communication function (e.g., a smart watch), or a non-portable terminal device such as a vehicle-mounted computer or a desktop computer. The resource server 13 may be deployed in a server that provides service support. The server may be one server or a combination of multiple servers, and the server may be an independent physical server, or may be a cloud server that provides basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, web service, cloud communication, middleware service, domain name service, security service, Content Delivery Network (CDN), big data, an artificial intelligence platform, and the like. Similarly, the dynamic interface server 14 may also be deployed in a server providing service support. The agent middleware 12 may be deployed in the same device as the client 11, for example, the agent middleware 12 may be deployed in a terminal device. The agent middleware 12 may also be deployed in the same device as the resource server 13, and the agent middleware 12 may also be deployed in the same device as the dynamic interface server 14. In addition to this, the proxy middleware 12 may be located in a separate device. And are not limited herein.
Based on the above description, the page data processing method according to the embodiment of the present application is explained in detail below. Referring to fig. 2, fig. 2 illustrates a page data processing method. As shown in fig. 2, the page data processing method includes S201 to S205:
s201: the target proxy middleware receives a first page request from a target client.
Wherein, the proxy middleware can refer to a component running in a browser or a thread. The proxy middleware is a transfer station between the client and the server. When the page data needs to be acquired, the target client initiates a page request, and the target agent middleware can intercept the page request. The target client may be any one of the clients in the page data processing system, and the target proxy middleware may be a proxy middleware corresponding to the target client. The page request may be any page request related to the embodiment of the present application, for example, a first page request or a second page request.
To facilitate client and server decoupling, proxy middleware may be deployed between the client and server. Optionally, an agent middleware may be deployed for one client, and the page request of the target client is intercepted by the target agent middleware corresponding to the target client.
Optionally, a proxy middleware may be deployed for a type of client. The type of the client may include, but is not limited to, a Hybrid type client and a Web type client. In one embodiment, when a target client generates a page request, the target client may send the page request to all proxy middleware, one proxy middleware may obtain a type of the target client carried in the page request when receiving the page request of the target client, and when the type of the target client matches a client type supported by the proxy middleware, the proxy middleware is the target proxy middleware and intercepts the page request of the target client. In another embodiment, the target client may send the page request to target proxy middleware that supports the target client type, the target proxy middleware intercepting the page request of the target client.
Optionally, a set of proxy middleware may be deployed for a client for load balancing. When a target client generates a page request, the target client can acquire load data of each proxy middleware in a group of proxy middleware corresponding to the target client, determine the target proxy middleware according to the load data of each proxy middleware, and send the page request to the target proxy middleware.
S202: when the target agent middleware determines that the first page request is processed, first data to be rendered corresponding to the first page request is obtained.
In order to avoid repeatedly executing the operations of obtaining static resource data, obtaining dynamic interface data and/or assembling the static resource data and the dynamic interface data, the target proxy middleware may determine whether a page request is processed when the page request is received. When the page request is processed, the target proxy middleware can directly acquire data to be rendered corresponding to the page request. When the page request is not processed, the target proxy middleware may perform an operation of sending the first resource request to the static resource server and/or sending the second resource request to the dynamic interface server.
In one embodiment, when the target proxy middleware receives a first page request from a target client, the target proxy middleware may determine whether to process the first page request.
Optionally, the target agent middleware may determine whether to process the first page request according to the first identification information and the page identification list. Specifically, first identification information carried by a first page request may be acquired, and a page identification list is acquired, where the page identification list includes one or more reference information; and performing hit matching on the first identification information and each reference information in the page identification list, and determining that the first page request is processed when the reference information which is successfully hit matched with the first identification information exists in the page identification list. Wherein the page request indicated by the reference information is a processed page request.
Alternatively, the target agent middleware may determine whether to process the first page request directly according to the first identification information. In one embodiment, the first identification information may be one bit. When the first identification information is a first value, the target proxy middleware determines that the first page request is processed. When the first identification information is the second value, the target agent middleware determines that the first page request is not processed. Where the first value and the second value mentioned above refer to different bit values, for example, the first value may be "1", and the second value may be "0"; alternatively, the first value may be "0" and the second value may be "1". In another embodiment, the first identification information may also be a field. When the first identification information is the first field, the target agent middleware determines that the first page request is processed. When the first identification information is the second field, the target agent middleware determines that the first page request is not processed. Wherein the first field and the second field mentioned above refer to different fields, for example, the first field may be "true" and the second field may be "false"; alternatively, the first field may be "false" and the second field may be "true".
Optionally, when the target agent middleware determines that the first page request is processed, the first data to be rendered corresponding to the first page request may be directly obtained.
Optionally, when the target agent middleware determines that the first page request is not processed, the target agent middleware may send the first resource request to the static resource server and/or send the second resource request to the dynamic interface server, obtain static resource data from the static resource server and/or dynamic interface data from the dynamic interface server, assemble the static resource data and the dynamic interface data, and generate first to-be-rendered data corresponding to the first page request. The first resource request is used for acquiring static resource data in the first page data, and the second resource request is used for acquiring dynamic interface data in the first page data.
When the target agent middleware determines that the first page request is processed, the target agent middleware can directly acquire the first data to be rendered of the first page data without repeatedly executing the operations of acquiring the static resource data, acquiring the dynamic interface data and/or assembling the static resource data and the dynamic interface data, so that the computing resources can be saved.
S203: and the target agent middleware receives a second page request from the target client and acquires second data to be rendered corresponding to the second page request.
It should be noted that the operation of the target proxy middleware for processing the second page request is similar to the operation of the target proxy middleware for processing the first page request. When the target agent middleware determines that the second page request is processed, the target agent middleware may directly obtain second data to be rendered corresponding to the second page request. When the target proxy middleware determines that the second page request is not processed, the target proxy middleware may perform an operation of sending the first resource request to the static resource server and/or sending the second resource request to the dynamic interface server. For a specific implementation, reference may be made to the description of S202, which is not described herein.
S204: and the target agent middleware determines the difference data according to the second data to be rendered and the first data to be rendered.
The difference data may refer to data different from the first data to be rendered in the second data to be rendered.
In one embodiment, the target agent middleware may obtain a template function, and generate a first virtual object model corresponding to the first data to be rendered and generate a second virtual object model corresponding to the second data to be rendered based on the template function. Discriminative data is then determined from the second virtual object model and the first virtual object model.
Optionally, the target agent middleware may obtain a template string; obtaining a template function character string based on the template character string; and taking the template function character string as the input of a preset general function to generate a template function. The template function is used to generate a virtual object model (virtual DOM).
Specifically, the target agent middleware may input the first data to be rendered into the template function to obtain a first virtual object model corresponding to the first data to be rendered, input the second data to be rendered into the template function to obtain a second virtual object model corresponding to the second data to be rendered, compare the second virtual object model with the first virtual object model, and determine that data different from the first virtual object model in the second virtual object model is distinct data, or, determine that data not belonging to the first virtual object model in the second virtual object model is distinct data.
S205: the target agent middleware sends the first data to be rendered and the distinguishing data to the target client, so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data.
In one embodiment, the target proxy middleware may send the first data to be rendered to the target client. The target client can render the first data to be rendered to generate first page data.
In one embodiment, the target proxy middleware may send the second data to be rendered to the target client. The target client can render the second data to be rendered to generate second page data.
In another embodiment, the target proxy middleware may also send the difference data to the target client. The target client may render the difference data and determine second page data according to the rendered difference data and the first page data. When the target client generates the second page data, the page data in the first page data can be multiplexed, the target client only needs to render the distinguishing data, all data in the second data to be rendered are not needed to be rendered, and computing resources of the client can be saved.
In one embodiment, the first page data may be pre-loaded page data as the second page data. When the difference data is smaller than the preset threshold, the similarity between the second data to be rendered and the first data to be rendered is higher, so that the similarity between the second page data obtained by rendering the second data to be rendered and the first page data obtained by rendering the first data to be rendered is also higher, and the first page data can be used as the preloaded page data of the second page data. When the target client displays the second page data, the target client skips to display the second page data by displaying the preloaded page data (the first page data), the page data is not updated in a full amount, the visual change is small, the page flicker is avoided, the page second opening can be realized, and the user experience is improved.
It should be noted that the preset threshold may be set according to experience or business requirements, and is not limited herein. The first page data and/or the second page data may include medical data, such as personal health record, prescription, examination report, and the like.
In this embodiment of the present application, the target proxy middleware may receive a first page request from a target client, and when it is determined that the first page request has been processed, obtain first data to be rendered corresponding to the first page request, then receive a second page request from the target client, and obtain second data to be rendered corresponding to the second page request; determining distinguishing data according to the second data to be rendered and the first data to be rendered; and sending the first data to be rendered and the distinguishing data to the target client so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data. When the target agent middleware determines that the first page request is processed, the first data to be rendered corresponding to the first page request can be directly acquired, and the target agent middleware does not need to repeatedly execute the operations of acquiring static resource data, acquiring dynamic interface data and assembling the static resource data and the dynamic interface data, so that the computing resources can be saved. In addition, the target agent middleware can also determine the difference data according to the second data to be rendered and the first data to be rendered, so that the target client can generate the second page data based on the first page data and the difference data after generating the first page data, the rendered first page data can be multiplexed, repeated rendering is avoided, and computing resources are saved.
As can be seen from the above description of the embodiment of the method shown in fig. 2, the page data processing method shown in fig. 2 can save computing resources. When the target agent middleware determines that the page request is not processed, the target agent middleware needs to acquire static resource data from the resource server and dynamic interface data from the dynamic interface server, and assemble the static resource data and the dynamic interface data to generate data to be rendered. Based on the page data processing method, the embodiment of the application also provides another page data processing method; referring to fig. 3, the page data processing method may include S301 to S306:
s301: the target client sends a first page request to the target proxy middleware.
S302: and when the first page request is determined not to be processed, the target proxy middleware sends the first resource request to the static resource server and/or sends the second resource request to the dynamic interface server.
The first resource request is used for acquiring static resource data in the first page data. Static resources may include, but are not limited to, one or more of HyperText Markup Language (HTML) structure resources, JavaScript script resources, Cascading Style Sheets (CSS) resources.
And the second resource request is used for acquiring the dynamic interface data in the first page data. The second resource request may be an HTTP network request, which is an application layer protocol. The target proxy middleware and the dynamic interface server can establish socket (socket) connection, and after the socket connection is successfully established, the target proxy middleware can initiate a second resource request to the dynamic interface server, wherein the second resource request is generally in a get or post mode.
It should be noted that, in order to save computing resources and/or storage resources, the acquired static resource data and/or dynamic interface data may also be reused. When the static resource data in the first page data exists in the target agent middleware, the target agent middleware may send the second resource request only to the dynamic interface server. When the dynamic interface data in the first page data exists in the target agent middleware, the target agent middleware may send the first resource request only to the static resource server.
S303: and the static resource server side responds to the first resource request and sends the static resource data to the target agent middleware.
Specifically, taking HTML structural resources as an example, when the URL address of the first resource request is a URL: and when http:// xx.com.cn/a. html, the target agent middleware can send the first resource request to the static resource server through the URL address of the first resource request, and the static resource server can respond to the first resource request to obtain the corresponding html resource file and return the html resource file to the target agent middleware.
Alternatively, the html resource file may be a medical data file, such as personal health profile, prescription, examination report, etc.
It should be noted that in one possible implementation, the data is medical data, such as personal health records, prescriptions, examination reports, and the like.
S304: and the dynamic interface server responds to the second resource request and sends the dynamic interface data to the target agent middleware.
After receiving a second resource request sent by the target agent middleware, the dynamic interface server processes corresponding interface logic according to the second resource request, wherein the second resource request is different, the corresponding interface is different, and the interface logic of different interfaces is different, for example, the interface for inquiring the information list, the interface processing logic is the interface for inquiring the news list, paging is carried out, the information list of the first page of classified content is returned, and the information list is returned to the target agent middleware.
It should be noted that, no precedence order exists between S303 and S304, and the steps may be executed simultaneously, or S303 and then S304 may be executed first, or S304 and then S303 may be executed first, which is not limited in this embodiment of the present application.
S305: and the target agent middleware generates first data to be rendered corresponding to the first page request according to the static resource data and the dynamic interface data.
The data to be rendered related to the embodiment of the application can be html codes of pages for rendering and displaying. When the target client side obtains the data to be rendered, the data to be rendered can be directly rendered to obtain page data.
Further, in an embodiment, the target agent middleware may store the data to be rendered and associate the data to be rendered with the page request, so that when the target agent middleware determines that the page request has been processed, the data to be rendered corresponding to the page request may be directly acquired.
Optionally, the target agent middleware may associate the data to be rendered with the page request according to a data protocol. The data protocol comprises an identification information field and a data field to be rendered. The identification information list item is used for storing identification information carried by the page request, for example, first identification information carried by the first page request. And the data list items to be rendered are used for storing data to be rendered. When the target agent middleware assembles the static resource data and the dynamic interface data to obtain data to be rendered, first identification information carried by the first page request may be stored at a first position of the identification information field, and the first data to be rendered may be stored at a position corresponding to the first position in the data field to be rendered. The first page request indicated by the first identification information stored at the first position of the identification information field is associated with the first data to be rendered stored at a position in the data to be rendered field corresponding to the first position.
Further, in an embodiment, for data security, the associated identification information field and data to be rendered field may also be written into a Block Chain (Block Chain), so that when the target proxy middleware determines that the page request indicated by the identification information in the identification information field has been processed, the data to be rendered in the data to be rendered field is acquired from the Block Chain. Specifically, the target agent middleware may verify the associated identification information field and the data field to be rendered, and if the verification is passed, perform consensus verification on the associated identification information field and the data field to be rendered through a consensus node in the blockchain network; and if the consensus verification is passed, packaging the associated identification information field and the data field to be rendered into a block, and writing the block into a block chain.
The block chain is a chain data structure formed by combining data blocks in a sequential connection mode according to a time sequence, and a distributed account book which ensures data to be not falsified and forged in a cryptographic mode is provided. Multiple independent distributed nodes maintain the same record. The blockchain technology realizes decentralization and becomes a foundation for credible digital asset storage, transfer and transaction.
S306: and the target agent middleware sends the first data to be rendered to the target client.
In this embodiment of the application, when the target proxy middleware determines that the first page request is not processed, the target proxy middleware may obtain static resource data from the resource server through the first resource request and/or obtain dynamic interface data from the dynamic interface server through the second resource request, and assemble the static resource data and the dynamic interface server to obtain data to be rendered. The target agent middleware decouples the client and the server. In addition, the target client can directly obtain the data to be rendered only by initiating the page request once, so that the steps of reducing the flow can be saved, the time delay is reduced, and the user experience is improved.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a page data processing apparatus according to an embodiment of the present disclosure. The page data processing apparatus may be the target proxy middleware mentioned in the foregoing method embodiments, and the page data processing apparatus may include an obtaining unit 401, a determining unit 402, and a sending unit 403.
An obtaining unit 401, configured to receive a first page request from a target client, and when it is determined that the first page request is processed, obtain first data to be rendered corresponding to the first page request;
the obtaining unit 401 is further configured to receive a second page request from the target client, and obtain second data to be rendered corresponding to the second page request;
a determining unit 402, configured to determine difference data according to the second data to be rendered and the first data to be rendered;
a sending unit 403, configured to send the first data to be rendered and the difference data to the target client, so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the difference data.
In some possible embodiments, the determining unit 402 is configured to determine the difference data according to the second data to be rendered and the first data to be rendered, and includes:
acquiring a template function, and generating a first virtual object model corresponding to first data to be rendered and a second virtual object model corresponding to second data to be rendered based on the template function;
the distinguishing data is determined from the second virtual object model and the first virtual object model.
In some possible embodiments, the obtaining unit 401 is configured to determine that the first page request is processed, and includes:
acquiring first identification information carried by a first page request;
acquiring a page identification list, wherein the page identification list comprises one or more reference information;
performing hit matching on the first identification information and each reference information in the page identification list;
and when the reference information which is successfully matched with the first identification information in a hit mode exists in the page identification list, determining that the first page request is processed.
In some possible embodiments, the obtaining unit 401 is configured to determine that the first page request is processed, and includes:
acquiring first identification information carried by a first page request;
when the first identification information is a first value, it is determined that the first page request has been processed.
In some possible embodiments, after the obtaining unit 401 is configured to receive the first page request from the target client, the obtaining unit 401 is further configured to:
when the first page request is determined to be unprocessed, sending a first resource request to a static resource server and sending a second resource request to a dynamic interface server, wherein the first resource request is used for acquiring static resource data in the first page data; the second resource request is used for acquiring dynamic interface data in the first page data;
acquiring static resource data from a static resource server and dynamic interface data from a dynamic interface server;
and assembling the static resource data and the dynamic interface data to generate first data to be rendered corresponding to the first page request.
It can be understood that each unit of the page data processing apparatus in this embodiment can be specifically implemented according to the method in the foregoing method embodiment fig. 2 or fig. 3, and the specific implementation process thereof may refer to the description related to the method embodiment fig. 2 or fig. 3, which is not described herein again.
In this embodiment of the present application, the page data processing apparatus may receive a first page request from a target client, and when it is determined that the first page request has been processed, obtain first data to be rendered corresponding to the first page request, then receive a second page request from the target client, and obtain second data to be rendered corresponding to the second page request; determining distinguishing data according to the second data to be rendered and the first data to be rendered; and sending the first data to be rendered and the distinguishing data to the target client so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data. When the page data processing device determines that the first page request is processed, the first data to be rendered corresponding to the first page request can be directly acquired, and the page data processing device does not need to repeatedly execute operations of acquiring static resource data, acquiring dynamic interface data and/or assembling the static resource data and the dynamic interface data, so that computing resources can be saved. In addition, the page data processing device can also determine the difference data according to the second data to be rendered and the first data to be rendered, so that the target client can generate the second page data based on the first page data and the difference data after generating the first page data, the rendered first page data can be multiplexed, repeated rendering is avoided, and computing resources are saved.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a page data processing apparatus according to an embodiment of the present disclosure. The page data processing device may be the target client mentioned in the foregoing method embodiments, and the page data processing device may include a sending unit 501 and a processing unit 502.
A sending unit 501, configured to send a first page request and a second page request to a target proxy middleware;
a processing unit 502 for receiving first data to be rendered and the difference data from the target agent middleware, and generating first page data based on the first data to be rendered and second page data based on the first page data and the difference data; the first data to be rendered is first data to be rendered corresponding to the first page request; the difference data is determined by the target agent middleware according to the first data to be rendered and the second data to be rendered, and the second data to be rendered is the second data to be rendered corresponding to the second page request.
In some possible embodiments, when the first page request is unprocessed, the first data to be rendered corresponding to the first page request is determined by the target agent middleware based on the static resource data and the dynamic interface data assembly; the static resource data is acquired from the static resource server by the target agent middleware in response to the first page request; the dynamic interface data is obtained by the target agent middleware from the dynamic interface server in response to the first page request.
It can be understood that each unit of the page data processing apparatus in this embodiment can be specifically implemented according to the method in the foregoing method embodiment fig. 2 or fig. 3, and the specific implementation process thereof may refer to the description related to the method embodiment fig. 2 or fig. 3, which is not described herein again.
In this embodiment of the present application, the target proxy middleware may receive a first page request from the page data processing apparatus, and when it is determined that the first page request has been processed, obtain first data to be rendered corresponding to the first page request, then receive a second page request from the page data processing apparatus, and obtain second data to be rendered corresponding to the second page request; determining distinguishing data according to the second data to be rendered and the first data to be rendered; the first data to be rendered and the difference data are sent to a page data processing apparatus so that the page data processing apparatus generates first page data based on the first data to be rendered and generates second page data based on the first page data and the difference data. When the target agent middleware determines that the first page request is processed, the first data to be rendered corresponding to the first page request can be directly acquired, and the target agent middleware does not need to repeatedly execute the operations of acquiring static resource data, acquiring dynamic interface data and/or assembling the static resource data and the dynamic interface data, so that the computing resources can be saved. In addition, the target agent middleware can also determine the difference data according to the second data to be rendered and the first data to be rendered, so that the page data processing device can generate the second page data based on the first page data and the difference data after generating the first page data, the rendered first page data can be multiplexed, repeated rendering is avoided, and computing resources are saved.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a page data processing apparatus according to an embodiment of the present disclosure. The page data processing apparatus may include: one or more processors 601; one or more input interfaces 602, one or more output interfaces 603, and computer storage media 604. The processor 601, the input interface 602, the output interface 603, and the computer storage medium 604 are connected by a bus or other means. The computer storage medium 604 is a memory device in the page data processing device for storing programs and data. It is understood that the computer storage medium 604 herein may include a built-in storage medium of the page data processing apparatus, and may also include an extended storage medium supported by the page data processing apparatus. Computer storage media 604 provides storage space that stores the operating system of the paged data processing device. Also stored in this memory space are one or more instructions, which may be one or more computer programs (including program code), suitable for loading and execution by processor 601. Note that the computer storage media herein can be high-speed RAM memory; optionally, the system may further include at least one computer storage medium remote from the processor, where the processor may be referred to as a Central Processing Unit (CPU), and is a core and a control center of the page data Processing device, and the processor is adapted to implement one or more instructions, specifically load and execute the one or more instructions, so as to implement the corresponding method flow or function.
In one embodiment, one or more instructions stored in the computer storage medium 604 may be loaded and executed by the processor 601 to implement the steps involved in performing the corresponding method as shown in fig. 2 or fig. 3, and in particular, one or more instructions stored in the computer storage medium 604 may be loaded and executed by the processor 601 to implement the steps of:
receiving a first page request from a target client, and acquiring first data to be rendered corresponding to the first page request when the first page request is determined to be processed;
receiving a second page request from the target client, and acquiring second data to be rendered corresponding to the second page request;
determining distinguishing data according to the second data to be rendered and the first data to be rendered;
and sending the first data to be rendered and the distinguishing data to the target client so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data.
In some possible embodiments, the processor 601 is configured to determine the difference data according to the second data to be rendered and the first data to be rendered, and includes:
acquiring a template function, and generating a first virtual object model corresponding to first data to be rendered and a second virtual object model corresponding to second data to be rendered based on the template function;
the distinguishing data is determined from the second virtual object model and the first virtual object model.
In some possible embodiments, the processor 601 is configured to determine that the first page request has been processed, and includes:
acquiring first identification information carried by a first page request;
acquiring a page identification list, wherein the page identification list comprises one or more reference information;
performing hit matching on the first identification information and each reference information in the page identification list;
and when the reference information which is successfully matched with the first identification information in a hit mode exists in the page identification list, determining that the first page request is processed.
In some possible embodiments, the processor 601 is configured to determine that the first page request has been processed, and includes:
acquiring first identification information carried by a first page request;
when the first identification information is a first value, it is determined that the first page request has been processed.
In some possible embodiments, after the processor 601 is configured to receive the first page request from the target client, the processor 601 is further configured to:
when the first page request is determined to be unprocessed, sending a first resource request to a static resource server and sending a second resource request to a dynamic interface server, wherein the first resource request is used for acquiring static resource data in the first page data; the second resource request is used for acquiring dynamic interface data in the first page data;
acquiring static resource data from a static resource server and dynamic interface data from a dynamic interface server;
and assembling the static resource data and the dynamic interface data to generate first data to be rendered corresponding to the first page request.
In the embodiment of the application, the page data processing device may receive a first page request from a target client, and when it is determined that the first page request has been processed, obtain first data to be rendered corresponding to the first page request, then receive a second page request from the target client, and obtain second data to be rendered corresponding to the second page request; determining distinguishing data according to the second data to be rendered and the first data to be rendered; and sending the first data to be rendered and the distinguishing data to the target client so that the target client generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data. When the page data processing device determines that the first page request is processed, the first data to be rendered corresponding to the first page request can be directly acquired, and the page data processing device does not need to repeatedly execute operations of acquiring static resource data, acquiring dynamic interface data, and/or assembling the static resource data and the dynamic interface data, so that computing resources can be saved. Moreover, the page data processing device can also determine the difference data according to the second data to be rendered and the first data to be rendered, so that the target client can generate the second page data based on the first page data and the difference data after generating the first page data, the rendered first page data can be multiplexed, repeated rendering is avoided, and computing resources are saved.
Referring to fig. 7, fig. 7 is a schematic structural diagram of another page data processing apparatus according to an embodiment of the present application. The page data processing apparatus may include: one or more processors 701; one or more input interfaces 702, one or more output interfaces 703, and computer storage media 704. The processor 701, the input interface 702, the output interface 703, and the computer storage medium 704 are connected by a bus or other means. The computer storage medium 704 is a memory device in the page data processing device for storing programs and data. It is understood that the computer storage medium 704 herein may include both a built-in storage medium of the page data processing apparatus and, of course, an extended storage medium supported by the page data processing apparatus. Computer storage media 704 provides storage space that stores the operating system of the page data processing apparatus. Also stored in this memory space are one or more instructions, which may be one or more computer programs (including program code), suitable for loading and execution by processor 701. Note that the computer storage media herein can be high-speed RAM memory; optionally, the system may further include at least one computer storage medium remote from the processor, where the processor may be referred to as a Central Processing Unit (CPU), and is a core and a control center of the page data Processing device, and the processor is adapted to implement one or more instructions, specifically load and execute the one or more instructions, so as to implement the corresponding method flow or function.
In one embodiment, one or more instructions stored in the computer storage medium 704 may be loaded and executed by the processor 701 to implement the steps involved in performing the corresponding method as shown in fig. 2 or fig. 3, and in particular, one or more instructions stored in the computer storage medium 704 may be loaded and executed by the processor 701 to implement the steps of:
sending a first page request and a second page request to the target proxy middleware;
receiving first data to be rendered and distinguishing data from the target agent middleware, generating first page data based on the first data to be rendered, and generating second page data based on the first page data and the distinguishing data; the first data to be rendered is first data to be rendered corresponding to the first page request; the difference data is determined by the target agent middleware according to the first data to be rendered and the second data to be rendered, and the second data to be rendered is the second data to be rendered corresponding to the second page request.
In some possible embodiments, when the first page request is unprocessed, the first data to be rendered corresponding to the first page request is determined by the target agent middleware based on the static resource data and the dynamic interface data assembly; the static resource data is acquired from the static resource server by the target agent middleware in response to the first page request; the dynamic interface data is obtained by the target agent middleware from the dynamic interface server in response to the first page request.
In this embodiment of the present application, the target proxy middleware may receive a first page request from the page data processing device, and when it is determined that the first page request has been processed, obtain first data to be rendered corresponding to the first page request, then receive a second page request from the page data processing device, and obtain second data to be rendered corresponding to the second page request; determining distinguishing data according to the second data to be rendered and the first data to be rendered; the first data to be rendered and the difference data are transmitted to the page data processing apparatus, so that the page data processing apparatus generates first page data based on the first data to be rendered and generates second page data based on the first page data and the difference data. When the target agent middleware determines that the first page request is processed, the first data to be rendered corresponding to the first page request can be directly acquired, and the target agent middleware does not need to repeatedly execute the operations of acquiring static resource data, acquiring dynamic interface data and/or assembling the static resource data and the dynamic interface data, so that the computing resources can be saved. In addition, the target agent middleware can also determine the difference data according to the second data to be rendered and the first data to be rendered, so that the page data processing equipment can generate the second page data based on the first page data and the difference data after generating the first page data, the rendered first page data can be multiplexed, repeated rendering is avoided, and computing resources are saved.
A computer-readable storage medium having computer program instructions stored thereon is also provided in embodiments of the present application. When executed by a processor, the computer program instructions may perform the steps performed in the above-described embodiments of the page data processing method.
An embodiment of the present application further provides a computer program product, where the computer program product includes a computer program code, and when the computer program code runs on a computer, the computer is caused to execute the steps executed in the above-mentioned page data processing method embodiment.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like. The computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the blockchain node, and the like.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1. A page data processing method is characterized by comprising the following steps:
receiving a first page request from a target client, and acquiring first to-be-rendered data corresponding to the first page request when the first page request is determined to be processed;
receiving a second page request from the target client, and acquiring second data to be rendered corresponding to the second page request;
determining distinguishing data according to the second data to be rendered and the first data to be rendered;
and sending the first data to be rendered and the distinguishing data to the target client side, so that the target client side generates first page data based on the first data to be rendered and generates second page data based on the first page data and the distinguishing data.
2. The method of claim 1, wherein the determining discriminative data from the second data to be rendered and the first data to be rendered comprises:
acquiring a template function, and generating a first virtual object model corresponding to the first data to be rendered and a second virtual object model corresponding to the second data to be rendered based on the template function;
determining the difference data from the second virtual object model and the first virtual object model.
3. The method of claim 1 or 2, wherein the determining that the first page request has been processed comprises:
acquiring first identification information carried by the first page request;
acquiring a page identification list, wherein the page identification list comprises one or more reference information;
performing hit matching on the first identification information and each reference information in the page identification list;
and when reference information which is successfully matched with the first identification information in a hit mode exists in the page identification list, determining that the first page request is processed.
4. The method of claim 1 or 2, wherein the determining that the first page request has been processed comprises:
acquiring first identification information carried by the first page request;
when the first identification information is a first value, determining that the first page request is processed.
5. The method of claim 1 or 2, wherein after receiving the first page request from the target client, the method further comprises:
when the first page request is determined not to be processed, sending a first resource request to a static resource server and sending a second resource request to a dynamic interface server, wherein the first resource request is used for acquiring static resource data in the first page data; the second resource request is used for acquiring dynamic interface data in the first page data;
acquiring static resource data from the static resource server and dynamic interface data from the dynamic interface server;
and assembling the static resource data and the dynamic interface data to generate first data to be rendered corresponding to the first page request.
6. A page data processing method is characterized by comprising the following steps:
sending a first page request and a second page request to the target proxy middleware;
receiving first data to be rendered and distinguishing data from the target agent middleware, generating first page data based on the first data to be rendered, and generating second page data based on the first page data and the distinguishing data; the first data to be rendered is first data to be rendered corresponding to the first page request; the difference data is determined by the target agent middleware according to the first data to be rendered and the second data to be rendered, and the second data to be rendered is the second data to be rendered corresponding to the second page request.
7. The method of claim 6, wherein when the first page request is unprocessed, the first data to be rendered corresponding to the first page request is determined by the target agent middleware based on static resource data and dynamic interface data assembly; the static resource data is acquired from a static resource server by the target agent middleware in response to the first page request; and the dynamic interface data is acquired from a dynamic interface server by the target agent middleware in response to the first page request.
8. A page data processing apparatus, characterized in that the apparatus comprises:
the system comprises an acquisition unit, a processing unit and a display unit, wherein the acquisition unit is used for receiving a first page request from a target client and acquiring first data to be rendered corresponding to the first page request when the first page request is determined to be processed;
the obtaining unit is further configured to receive a second page request from the target client, and obtain second data to be rendered corresponding to the second page request;
a determining unit, configured to determine difference data according to the second data to be rendered and the first data to be rendered;
a sending unit, configured to send the first data to be rendered and the difference data to the target client, so that the target client generates first page data based on the first data to be rendered, and generates second page data based on the first page data and the difference data.
9. A page data processing apparatus, comprising a processor and a memory, wherein the memory is configured to store a computer program, the computer program comprising a program, and the processor is configured to invoke the program to perform the page data processing method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to execute the page data processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111011994.3A CN113704648A (en) | 2021-08-31 | 2021-08-31 | Page data processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111011994.3A CN113704648A (en) | 2021-08-31 | 2021-08-31 | Page data processing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113704648A true CN113704648A (en) | 2021-11-26 |
Family
ID=78657926
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111011994.3A Pending CN113704648A (en) | 2021-08-31 | 2021-08-31 | Page data processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113704648A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114401307A (en) * | 2022-01-19 | 2022-04-26 | 平安国际智慧城市科技股份有限公司 | Data request method, system and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105607927A (en) * | 2015-12-18 | 2016-05-25 | 小米科技有限责任公司 | Page display method and apparatus |
| CN108241703A (en) * | 2016-12-27 | 2018-07-03 | 腾讯科技（深圳）有限公司 | Web data transmission method and device |
| CN108572819A (en) * | 2017-12-21 | 2018-09-25 | 北京金山云网络技术有限公司 | Method for updating pages, device, terminal and computer readable storage medium |
| CN111708600A (en) * | 2020-08-20 | 2020-09-25 | 腾讯科技（深圳）有限公司 | Page display method, device, equipment and computer readable storage medium |
| CN112836152A (en) * | 2019-11-22 | 2021-05-25 | 上海哔哩哔哩科技有限公司 | Page rendering method, system, computer device and computer readable storage medium |
-
2021
- 2021-08-31 CN CN202111011994.3A patent/CN113704648A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105607927A (en) * | 2015-12-18 | 2016-05-25 | 小米科技有限责任公司 | Page display method and apparatus |
| CN108241703A (en) * | 2016-12-27 | 2018-07-03 | 腾讯科技（深圳）有限公司 | Web data transmission method and device |
| CN108572819A (en) * | 2017-12-21 | 2018-09-25 | 北京金山云网络技术有限公司 | Method for updating pages, device, terminal and computer readable storage medium |
| CN112836152A (en) * | 2019-11-22 | 2021-05-25 | 上海哔哩哔哩科技有限公司 | Page rendering method, system, computer device and computer readable storage medium |
| CN111708600A (en) * | 2020-08-20 | 2020-09-25 | 腾讯科技（深圳）有限公司 | Page display method, device, equipment and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114401307A (en) * | 2022-01-19 | 2022-04-26 | 平安国际智慧城市科技股份有限公司 | Data request method, system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107622135B (en) | Method and apparatus for displaying information | |
| EP3518124A1 (en) | Webpage rendering method and related device | |
| CN110245069B (en) | Page version testing method and device and page display method and device | |
| CN109543454B (en) | Anti-crawler method and related equipment | |
| US8527862B2 (en) | Methods for making ajax web applications bookmarkable and crawlable and devices thereof | |
| CN103605502B (en) | Form page display method and server | |
| CN107315646B (en) | Method and device for controlling data flow between page components | |
| EP3528474B1 (en) | Webpage advertisement anti-shielding methods and content distribution network | |
| CN111431767B (en) | Multi-browser resource synchronization method and device, computer equipment and storage medium | |
| CN113704648A (en) | Page data processing method, device, equipment and storage medium | |
| CN111273964B (en) | Data loading method and device | |
| CN113703979A (en) | Resource processing method and device, resource processing equipment and storage medium | |
| CN110088750B (en) | Method and system for providing context function in static webpage | |
| CN115421693A (en) | Method and device for realizing micro front-end architecture, computer equipment and storage medium | |
| CN111444448B (en) | Data processing method, server and system | |
| CN112434233B (en) | Method and device for accelerating first screen rendering of secondary page | |
| CN105589870B (en) | Method and system for filtering webpage advertisements | |
| CN112565472B (en) | Static resource processing method and device | |
| US11258845B2 (en) | Browser management system, browser management method, browser management program, and client program | |
| CN110505258A (en) | Webpage load and response method, device, computer equipment and storage medium | |
| RU2638015C2 (en) | Method for identification of target object on web page | |
| CN108737133A (en) | Method and device for CDN static network reparations | |
| CN117786255A (en) | Method, device and system for loading Web page and computer readable storage medium | |
| CN117056629A (en) | Cache configuration method, device, computer equipment and storage medium | |
| CN113515710A (en) | Page information display method and device, electronic 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 |