CN112214699A - Page processing method and related device - Google Patents
Page processing method and related device Download PDFInfo
- Publication number
- CN112214699A CN112214699A CN201910623707.0A CN201910623707A CN112214699A CN 112214699 A CN112214699 A CN 112214699A CN 201910623707 A CN201910623707 A CN 201910623707A CN 112214699 A CN112214699 A CN 112214699A
- Authority
- CN
- China
- Prior art keywords
- request message
- login
- server
- target
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title abstract description 11
- 238000000034 method Methods 0.000 claims abstract description 47
- 238000012545 processing Methods 0.000 claims description 49
- 230000004044 response Effects 0.000 claims description 32
- 230000008569 process Effects 0.000 abstract description 14
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 238000012795 verification Methods 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000010079 rubber tapping Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010897 surface acoustic wave method 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/957—Browsing optimisation, e.g. caching or content distillation
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a page processing method and a related device, which save resources consumed in the process of generating a request message on one hand, and can improve the efficiency of page loading on the other hand, thereby realizing the efficient access of a new page. The method comprises the following steps: acquiring a first request message, wherein the first request message is used for requesting page data from a server; if the login operation needs to be executed according to the first request message, adding the first request message to a preset request queue; executing login operation; receiving a first login identification sent by a server; updating a first request message in a preset request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification; and sending the target request message to the server so that the server sends the page data according to the target request message.
Description
Technical Field
The present application relates to the field of network technologies, and in particular, to a page processing method and a related device.
Background
When a user accesses a page through a browser, some pages typically require the user to log in to continue browsing the page.
In the prior art, when a user starts a browser on a client to browse a page, the client generates a page data request message and sends the page data request message to a background server. If the page data request message does not carry a user login identifier (token) or an invalid token, the client needs to log in again, and after the login is completed, the client can obtain a new token and re-request page data to complete page rendering.
However, when the client requests the page data again, that is, the page needs to be reloaded, the current page of the browser is refreshed, so that the page is flashed, and the page display efficiency is reduced.
Disclosure of Invention
The embodiment of the application provides a page processing method and a related device, which save resources consumed in the process of generating a request message on the one hand, and can improve the page loading efficiency on the other hand, thereby realizing efficient access of a new page.
A first aspect of the embodiments of the present application provides a method for page processing, including:
acquiring a first request message, wherein the first request message is used for requesting page data from a server;
if the login operation needs to be executed according to the first request message, adding the first request message to a preset request queue;
executing login operation;
receiving a first login identification sent by the server;
updating the first request message in the preset request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification;
and sending the target request message to the server so that the server sends the page data according to the target request message.
A second aspect of the embodiments of the present application provides a page processing apparatus, including:
the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is used for acquiring a first request message which is used for requesting page data from a server;
the adding module is used for adding the first request message to a preset request queue if the login operation needs to be executed according to the first request message;
the login module is used for executing login operation;
the receiving module is used for receiving a first login identifier sent by the server;
the updating module is used for updating the first request message in the preset request queue according to the first login identification to obtain a target request message, and the target request message carries the first login identification;
and the sending module is used for sending the target request message to the server so that the server sends the page data according to the target request message.
Based on the second aspect, the embodiment of the present application further provides a first implementation manner of the second aspect:
the adding module is further configured to:
if the first request message does not carry a second login identifier, adding the first request message to a preset first request queue;
updating the first request message in the preset request queue according to the first login identifier to obtain a target request message, wherein the target request message carrying the first login identifier comprises:
and updating the first request message in the preset first request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
Based on the second aspect, the embodiment of the present application further provides a second implementation manner of the second aspect:
the adding module is further configured to:
if the first request message carries a second login identifier, sending the first request message to the server;
receiving a first response message, wherein the first response message corresponds to the first request message;
determining a second login identifier as an invalid identifier according to the first response message;
adding the first request message to a pre-provisioned second request queue;
updating the first request message in the preset request queue according to the first login identifier to obtain a target request message, wherein the target request message carrying the first login identifier comprises:
and updating the first request message in the preset second request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
Based on the second aspect, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, an embodiment of the present application further provides a third implementation manner of the second aspect:
the login module is further configured to:
and sending a second request message to the server, wherein the second request message is used for logging in the server.
Based on the third implementation manner of the second aspect, the embodiment of the present application further provides a fourth implementation manner of the second aspect:
the receiving module is further configured to:
and receiving a second response message of the server, wherein the second response message corresponds to the second request message and carries the first login identifier.
Based on the second aspect, or the first implementation manner of the second aspect, or the second implementation manner of the second aspect, an embodiment of the present application further provides a fifth implementation manner of the second aspect:
the update module is further to:
and adding the first login identification to the first request message in the preset request queue to obtain a target request message.
Based on the first implementation manner of the second aspect or the second implementation manner of the second aspect, an embodiment of the present application further provides a fifth implementation manner of the second aspect:
the page processing apparatus further includes:
and the emptying module is used for emptying the preset first request queue or the preset second request queue.
An embodiment of the present application further provides a terminal device, including: a memory, a transceiver, a processor, and a bus system;
wherein the memory is used for storing programs;
the processor is used for executing the program in the memory and comprises the following steps:
acquiring a first request message, wherein the first request message is used for requesting page data from a server;
if the login operation needs to be executed according to the first request message, adding the first request message to a preset request queue;
executing login operation;
receiving a first login identification sent by the server;
updating the first request message in the preset request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification;
sending the target request message to the server so that the server sends the page data according to the target request message;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
Embodiments of the present application also provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method according to the first aspect.
According to the technical scheme, the embodiment of the application has the following advantages:
the embodiment of the application provides a page processing method and a related device, wherein after a first request message for requesting page data is acquired, whether login operation is needed or not is judged according to the first request message. When login is needed, the first request message is put into a preset request queue, after the login is completed, the first login identification sent by the server is received, the first request message can be updated to obtain a target request message carrying the first login identification, and page data is successfully requested.
Drawings
FIG. 1 is a block diagram of a page processing system according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for processing a page in an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating an application of the method for page processing in the embodiment of the present application;
FIG. 4 is a schematic diagram illustrating another application of the method for page processing in the embodiment of the present application;
FIG. 5 is a schematic structural diagram of a page processing apparatus according to an embodiment of the present application;
fig. 6 is a block diagram of a partial structure of a mobile phone related to a terminal provided in an embodiment of the present application.
Detailed Description
The embodiment of the application provides a page processing method and a related device, which save resources consumed in the process of generating a request message on the one hand, and can improve the page loading efficiency on the other hand, thereby realizing efficient access of a new page.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "corresponding" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that the present application applies to a page access scenario, and in particular, the scenario generally refers to a data interaction process with a background server when a user browses a page through a browser on a client.
To facilitate understanding, an embodiment of the present application provides a method for page processing, which is applied to the page processing system shown in fig. 1, please refer to fig. 1, fig. 1 is a schematic structural diagram of the page processing system in the embodiment of the present application, and as shown in the drawing, the system includes: the client side is in communication connection with the server.
It should be understood that the client may include, but is not limited to, a terminal device such as a smart phone, a personal computer, a palm top computer, a television set top box, etc., for outputting an application graphical interface and sending an operation instruction input by a user through an input device such as a mouse, a keyboard, etc., to the server through the network.
When a user accesses a certain page for the first time through a browser on a client, a login operation is usually required, that is, user data is sent to a server for authentication. After the verification is passed, the server returns the login identification token of the user to the client, the client stores the token, generates a page data request carrying the token, and sends the page data request to the server. Due to the token, the server can provide corresponding page data to the client to render the page for the user to use.
The following describes a page processing method provided in an embodiment of the present application from the perspective of a client. Fig. 2 is a schematic flowchart of a method for processing a page in an embodiment of the present application, and referring to fig. 2, an embodiment of the method for processing a page in the embodiment of the present application includes:
201. acquiring a first request message, wherein the first request message is used for requesting page data from a server;
in this embodiment, when a user needs to access a page on a browser on a client, a first request message, which may be an ajax request, is generated, where the first request message is used to request page data from a server to render the page, so that the user can use the page.
202. If the login operation needs to be executed according to the first request message, adding the first request message to a preset request queue;
the client judges whether the login operation is needed or not based on the first request message. It should be noted that the client may determine multiple situations based on the first request message, where there are two situations that require login operation, and the two situations are described below separately:
(1) when a second login identification of the user exists in a local cache of the browser, a first request message generated by the client carries the second login identification, and the second login identification represents that the user has logged in the page before. However, after the server receives the first request message, the server may parse the first request message to obtain a second login identifier, perform state detection on the second login identifier, and if the second login identifier is an invalid identifier, the server notifies the client, so that the client determines that the second login identifier is invalid and needs to perform login operation again.
(2) When the second login identification of the user does not exist in the local cache of the browser, the first request message generated by the client does not carry the second login identification, and the fact that the user does not log in the page before can be determined. At this time, the client itself may determine that a login operation is required based on the first request message.
In this embodiment, after the client determines that the login operation needs to be performed according to the first request message, the client places the first request message into the preset request queue, and it should be understood that the preset request queue may be an array, and the first request message placed in the queue is in a state to be processed and can be continuously used in a subsequent flow.
203. Executing login operation;
after the client adds the first request message to the preset request queue, login operation can be performed. It is understood that the login operation is a verification process between the client and the server about the user data, and the server may return a valid first login identifier to the client after the login operation is completed.
204. Receiving a first login identification sent by a server;
after the client finishes the login operation, namely the user passes the login verification, at this time, the server side generates a first login identification corresponding to the user and returns the first login identification to the client, and the client can store the first login identification in a local cache of the browser to form the latest login identification representing the user.
205. Updating a first request message in a preset request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification;
in this embodiment, after the client obtains the first login identifier, the first request message in the preset request queue may be updated according to the first login identifier to obtain the target request message, and it is worth noting that the target request message is the updated first request message, which is equivalent to updating the parameter included in the original first request message, and thus the target request message carrying the first login identifier may be obtained.
206. And sending the target request message to the server so that the server sends the page data according to the target request message.
After the target request message is obtained, the client sends the target request message to the server, after the server receives the target request message, the server analyzes the target request message to obtain a first login identification, and the server can return corresponding page data, so that the client renders a complete page according to the page data for a user to use.
In this embodiment, since the preset request queue stores the first request message, the original first request message can be directly updated and reused for the data request, and a new request message does not need to be generated again, that is, a page does not need to be reloaded, so that resources consumed in the process of generating the request message are saved, and on the other hand, the page loading efficiency can be improved, thereby realizing efficient access to the new page.
Based on the foregoing embodiment, since the client determines that there are two cases in which the login operation is required, the subsequent processing of the first request message in the embodiment of the present application also has a difference in the two cases, and the two cases will be described separately below.
Optionally, based on the embodiment corresponding to fig. 2, in an optional embodiment of the method for processing a page in the embodiment of the present application, if it is determined that a login operation needs to be performed according to the first request message, adding the first request message to the preset request queue includes:
if the first request message does not carry the second login identification, adding the first request message to a preset first request queue;
according to the first login identification, updating a first request message in a preset request queue to obtain a target request message, wherein the target request message carrying the first login identification comprises:
and updating the first request message in the preset first request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
The present embodiment corresponds to the case where the first request message does not carry the second login identifier. And when the client determines that the first request message does not carry the second login identification, adding the first request message to a preset first request queue. It should be noted that the preset first request queue is used for storing page data requests without login identifiers.
Further, after the client finishes logging in to obtain the first login identifier, the first request message in the preset first request queue can be updated to obtain the target request message carrying the first login identifier.
Optionally, based on the embodiment corresponding to fig. 2, in an optional embodiment of the method for processing a page in the embodiment of the present application, if it is determined that a login operation needs to be performed according to the first request message, adding the first request message to the preset request queue includes:
if the first request message carries the second login identification, the first request message is sent to the server;
receiving a first response message, wherein the first response message corresponds to the first request message;
determining the second login identification as an invalid identification according to the first response message;
adding the first request message to a preset second request queue;
according to the first login identification, updating a first request message in a preset request queue to obtain a target request message, wherein the target request message carrying the first login identification comprises:
and updating the first request message in the preset second request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
This embodiment corresponds to the case where the first request message carries an invalid second login identifier. Specifically, the client sends a first request message carrying the second login identifier to the server, and the server analyzes the first request message to obtain the second login identifier. If the server determines that the second login identifier is invalid, if the second login identifier is expired, the server returns a first response message, where it can be understood that the first response message corresponds to the first request message, and the first response message is used to instruct the client to determine that the second login identifier is invalid.
After receiving the first response message, the client determines that the second login identification is invalid according to the first response message, and adds the first request message to a preset second request queue, wherein the preset second request queue is used for storing page data requests carrying invalid login identifications.
Further, after the client finishes logging in to obtain the first login identification, the first request message in the preset second request queue can be updated to obtain the target request message carrying the first login identification.
Optionally, based on each embodiment corresponding to fig. 2, in an optional embodiment of the method for processing a page in the embodiment of the present application, the executing the login operation includes:
and sending a second request message to the server, wherein the second request message is used for logging in the server.
Receiving the first login identification of the server comprises:
and receiving a second response message of the server, wherein the second response message corresponds to the second request message and carries the first login identifier.
In this embodiment, when the client performs the login operation, the client may send a second request message to the server, and it should be understood that the second request message is generally a login request message, and is used for logging in the server. In particular, the second request message typically contains user data, such as the user's account password, etc. And after receiving the second request message, the server can verify the user data in the second request message, and can return a second response message after the verification is passed, wherein the second response message corresponds to the second request message and carries the effective first login identification.
Optionally, based on each embodiment corresponding to fig. 2, in an optional embodiment of the page processing method in the embodiment of the present application, the updating is performed on the first request message in the preset request queue according to the first login identifier to obtain the target request message, where the target request message carrying the first login identifier includes:
and adding the first login identification to a first request message in a preset request queue to obtain a target request message.
In this embodiment, after the client analyzes the second response message to obtain the first login identifier, the client may add the first login identifier to the original first request message to obtain the target request message.
It should be noted that, because the first login identifier has two situations, that is, the first login identifier does not carry the second login identifier and carries the invalid second login identifier, after the client adds the first login identifier to the first request message, if the first login identifier is the first request message which does not carry the second login identifier, the target request message carrying the first login identifier may be obtained. If the first login request carries the invalid second login identification, the first login request replaces the second login request to obtain a target request message carrying the first login identification.
Optionally, based on each embodiment corresponding to fig. 2, in an optional embodiment of the method for processing a page in the embodiment of the present application, sending a target request message to a server, so that after the server sends page data according to the target request message, the method further includes:
and emptying the preset first request queue or the preset second request queue.
In this embodiment, when the client sends the target request message to the server, so that the server sends the page data according to the target request message, and after the page processing is completed, the preset first request queue or the preset second request queue may be emptied, so as to be used in the next page processing.
A specific application example will be provided to further describe the method for page processing in the embodiment of the present application, and fig. 3 is an application illustration diagram of the method for page processing in the embodiment of the present application. Referring to fig. 3, the application example includes:
301. entering a page;
the user launches a browser on the client to access the page.
302. The client judges whether the page data request carries a token;
if the page data request carries token, 303 is executed, and if the page data request does not carry token, 305 is executed.
303. The server receives the page data request and judges whether the token is overdue or not;
if token expires, the client is notified and the client proceeds to step 304.
304. The client puts the page data request into an overdue request queue;
it should be appreciated that the expired request queue, i.e., the pre-set second request queue described above, is then executed at step 306.
305. The client puts the page data request into a token-free request queue;
it should be appreciated that there is no token request queue, i.e., the pre-set first request queue described above, and then step 306 is performed.
306. The client performs login operation;
307. the server sends the logged token to the client;
308. the client updates the requests in the queue and resends the page data requests to the server;
and the client updates the request in the queue based on the logged token to obtain a page data request carrying the effective token, and sends the page data request to the client.
309. The client receives page data;
310. the queue is emptied.
For convenience of understanding, an application example when the number of the requests is multiple is described below with reference to fig. 4, and please refer to fig. 4, where fig. 4 is another application illustration view of the method for processing the page in the embodiment of the present application. The overall flow of the application example in fig. 4 is similar to the application example corresponding to fig. 3.
When the client sends a plurality of page data requests to the server at the same time, if none of the page data requests carries a token, the operation flow of the subsequent client is the same as that in fig. 3.
If multiple page data requests all carry expired tokens, the specific process is as shown in fig. 4:
401. the client sends a plurality of requests to the server;
402. the server determines whether the token is invalid;
and if so, notifying the client.
403. The client receives a first request response (corresponding to one of the page data requests) returned by the server;
and the client receives a first request response returned by the server and determines that the tokens in all the requests are invalid.
404. The client puts all page data requests into corresponding queues;
405. the client performs login operation;
and obtaining a new token after the client finishes logging in.
406. The client updates all page data requests in the queue according to the new token;
407. the client sends an updated certain page data request to the server, wherein the request corresponds to a first request response;
408. when the client side receives each request response successively, the client side does not need to log in any more, and correspondingly sends other updated page data requests.
By the page processing method in the embodiment, on one hand, resources consumed in the process of generating the request message are saved, and on the other hand, the page loading efficiency can be improved, so that the efficient access of the new page is realized.
The above is a detailed description of a method for processing a page in an embodiment of the present application, and a structure and a connection relationship of a page processing apparatus in the embodiment of the present application are described below, fig. 5 is a schematic structural diagram of the page processing apparatus in the embodiment of the present application, and please refer to fig. 5, an embodiment of the page processing apparatus in the embodiment of the present application includes:
an obtaining module 501, configured to obtain a first request message, where the first request message is used to request a server for page data;
an adding module 502, configured to add the first request message to a preset request queue if it is determined that the login operation needs to be executed according to the first request message;
a login module 503, configured to perform a login operation;
a receiving module 504, configured to receive a first login identifier sent by a server;
an updating module 505, configured to update a first request message in a preset request queue according to a first login identifier, to obtain a target request message, where the target request message carries the first login identifier;
a sending module 506, configured to send the target request message to the server, so that the server sends the page data according to the target request message.
Optionally, based on the embodiment corresponding to fig. 5, in an optional embodiment of the page processing apparatus in the embodiment of the present application, the adding module is further configured to:
if the first request message does not carry the second login identification, adding the first request message to a preset first request queue;
according to the first login identification, updating a first request message in a preset request queue to obtain a target request message, wherein the target request message carrying the first login identification comprises:
and updating the first request message in the preset first request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
Optionally, based on the embodiment corresponding to fig. 5, in an optional embodiment of the page processing apparatus in the embodiment of the present application, the adding module is further configured to:
if the first request message carries the second login identification, the first request message is sent to the server;
receiving a first response message, wherein the first response message corresponds to the first request message;
determining the second login identification as an invalid identification according to the first response message;
adding the first request message to a preset second request queue;
according to the first login identification, updating a first request message in a preset request queue to obtain a target request message, wherein the target request message carrying the first login identification comprises:
and updating the first request message in the preset second request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
Optionally, based on each embodiment corresponding to fig. 5, in an optional embodiment of the page processing apparatus in the embodiment of the present application, the login module is further configured to:
and sending a second request message to the server, wherein the second request message is used for logging in the server.
Optionally, based on each embodiment corresponding to fig. 5, in an optional embodiment of the page processing apparatus in the embodiment of the present application, the receiving module is further configured to:
and receiving a second response message of the server, wherein the second response message corresponds to the second request message and carries the first login identifier.
Optionally, based on each embodiment corresponding to fig. 5, in an optional embodiment of the page processing apparatus in the embodiment of the present application, the update module is further configured to:
and adding the first login identification to a first request message in a preset request queue to obtain a target request message.
Optionally, based on each embodiment corresponding to fig. 5, in an optional embodiment of the page processing apparatus in this embodiment of the application, the page processing apparatus further includes:
and the emptying module is used for emptying the preset first request queue or the preset second request queue.
As shown in fig. 6, for convenience of description, only the portions related to the embodiments of the present application are shown, and details of the specific technology are not disclosed, please refer to the method portion of the embodiments of the present application. The terminal may be any terminal device including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a point of sale (POS), a vehicle-mounted computer, and the like, taking the terminal as the mobile phone as an example:
fig. 6 is a block diagram illustrating a partial structure of a mobile phone related to a terminal provided in an embodiment of the present application. Referring to fig. 6, the handset includes: radio Frequency (RF) circuitry 610, memory 620, input unit 630, display unit 640, sensor 650, audio circuitry 660, wireless fidelity (WiFi) module 670, processor 680, and power supply 690. Those skilled in the art will appreciate that the handset configuration shown in fig. 6 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile phone in detail with reference to fig. 6:
the RF circuit 610 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, receives downlink information of a base station and then processes the received downlink information to the processor 680; in addition, the data for designing uplink is transmitted to the base station. In general, the RF circuit 610 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuitry 610 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), etc.
The memory 620 may be used to store software programs and modules, and the processor 680 may execute various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 620. The memory 620 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 by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 620 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The input unit 630 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 630 may include a touch panel 631 and other input devices 632. The touch panel 631, also referred to as a touch screen, may collect touch operations of a user (e.g., operations of the user on the touch panel 631 or near the touch panel 631 by using any suitable object or accessory such as a finger or a stylus) thereon or nearby, and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 631 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 680, and can receive and execute commands sent by the processor 680. In addition, the touch panel 631 may be implemented using various types, such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 630 may include other input devices 632 in addition to the touch panel 631. In particular, other input devices 632 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 640 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 640 may include a display panel 641, and optionally, the display panel 641 may be configured in the form of a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 631 can cover the display panel 641, and when the touch panel 631 detects a touch operation thereon or nearby, the touch panel is transmitted to the processor 680 to determine the type of the touch event, and then the processor 680 provides a corresponding visual output on the display panel 641 according to the type of the touch event. Although in fig. 6, the touch panel 631 and the display panel 641 are two independent components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 631 and the display panel 641 may be integrated to implement the input and output functions of the mobile phone.
The handset may also include at least one sensor 650, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that adjusts the brightness of the display panel 641 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 641 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 670, and provides wireless broadband Internet access for the user. Although fig. 6 shows the WiFi module 670, it is understood that it does not belong to the essential constitution of the handset, and can be omitted entirely as needed within the scope not changing the essence of the invention.
The processor 680 is a control center of the mobile phone, and connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 620 and calling data stored in the memory 620, thereby performing overall monitoring of the mobile phone. Optionally, processor 680 may include one or more processing units; optionally, the processor 680 may integrate an application processor and a modem processor, wherein the application processor mainly handles operating systems, user interfaces, application programs, and the like, and the modem processor mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 680.
The handset also includes a power supply 690 (e.g., a battery) for powering the various components, optionally, the power supply may be logically connected to the processor 680 via a power management system, so that the power management system may be used to manage charging, discharging, and power consumption.
Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.
In the embodiment of the present application, the processor 680 included in the terminal further has a function of performing each step of the above-described page processing method.
Embodiments of the present application also relate to a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform a method such as page processing.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. A method of page processing, comprising:
acquiring a first request message, wherein the first request message is used for requesting page data from a server;
if the login operation needs to be executed according to the first request message, adding the first request message to a preset request queue;
executing login operation;
receiving a first login identification sent by the server;
updating the first request message in the preset request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification;
and sending the target request message to the server so that the server sends the page data according to the target request message.
2. The method for processing pages of claim 1, wherein adding the first request message to a pre-configured request queue if it is determined that a login operation needs to be performed according to the first request message comprises:
if the first request message does not carry a second login identifier, adding the first request message to a preset first request queue;
updating the first request message in the preset request queue according to the first login identifier to obtain a target request message, wherein the target request message carrying the first login identifier comprises:
and updating the first request message in the preset first request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
3. The method for processing pages of claim 1, wherein adding the first request message to a pre-configured request queue if it is determined that a login operation needs to be performed according to the first request message comprises:
if the first request message carries a second login identifier, sending the first request message to the server;
receiving a first response message, wherein the first response message corresponds to the first request message;
determining a second login identifier as an invalid identifier according to the first response message;
adding the first request message to a pre-provisioned second request queue;
updating the first request message in the preset request queue according to the first login identifier to obtain a target request message, wherein the target request message carrying the first login identifier comprises:
and updating the first request message in the preset second request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification.
4. The method for page processing according to any of claims 1 to 3, wherein said performing a login operation comprises:
and sending a second request message to the server, wherein the second request message is used for logging in the server.
5. The method for page processing according to claim 4, wherein said receiving the first login identification of the server comprises:
and receiving a second response message of the server, wherein the second response message corresponds to the second request message and carries the first login identifier.
6. The method for processing the page according to any one of claims 1 to 3, wherein the updating the first request message in the preset request queue according to the first login identifier to obtain a target request message, where the target request message carrying the first login identifier includes:
and adding the first login identification to the first request message in the preset request queue to obtain a target request message.
7. The method for processing the page according to claim 2 or 3, wherein the sending the target request message to the server, so that the server further comprises, after sending the page data according to the target request message:
and emptying the preset first request queue or the preset second request queue.
8. A page processing apparatus, comprising:
the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is used for acquiring a first request message which is used for requesting page data from a server;
the adding module is used for adding the first request message to a preset request queue if the login operation needs to be executed according to the first request message;
the login module is used for executing login operation;
the receiving module is used for receiving a first login identifier sent by the server;
the updating module is used for updating the first request message in the preset request queue according to the first login identification to obtain a target request message, and the target request message carries the first login identification;
and the sending module is used for sending the target request message to the server so that the server sends the page data according to the target request message.
9. A terminal device, comprising: a memory, a transceiver, a processor, and a bus system;
wherein the memory is used for storing programs;
the processor is used for executing the program in the memory and comprises the following steps:
acquiring a first request message, wherein the first request message is used for requesting page data from a server;
if the login operation needs to be executed according to the first request message, adding the first request message to a preset request queue;
executing login operation;
receiving a first login identification sent by the server;
updating the first request message in the preset request queue according to the first login identification to obtain a target request message, wherein the target request message carries the first login identification;
sending the target request message to the server so that the server sends the page data according to the target request message;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
10. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910623707.0A CN112214699B (en) | 2019-07-10 | 2019-07-10 | Page processing method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910623707.0A CN112214699B (en) | 2019-07-10 | 2019-07-10 | Page processing method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112214699A true CN112214699A (en) | 2021-01-12 |
| CN112214699B CN112214699B (en) | 2023-11-07 |
Family
ID=74047607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910623707.0A Active CN112214699B (en) | 2019-07-10 | 2019-07-10 | Page processing method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112214699B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113448748A (en) * | 2021-06-03 | 2021-09-28 | 北京致远互联软件股份有限公司 | Refreshing method and refreshing system driven by message |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130139043A1 (en) * | 2011-11-29 | 2013-05-30 | OneScreen Inc. | System, apparatus and method for updating links |
| CN105141605A (en) * | 2015-08-19 | 2015-12-09 | 金蝶软件（中国）有限公司 | Session method, web server and browser |
| CN105162591A (en) * | 2015-07-07 | 2015-12-16 | 腾讯科技（深圳）有限公司 | Equipment registration method and device |
| CN107743134A (en) * | 2017-11-28 | 2018-02-27 | 湖北三新文化传媒有限公司 | Log-on message processing method, client, server and storage medium |
| CN108769041A (en) * | 2018-06-06 | 2018-11-06 | 深圳壹账通智能科技有限公司 | Login method, system, computer equipment and storage medium |
| CN109218389A (en) * | 2018-07-05 | 2019-01-15 | 东软集团股份有限公司 | The method, apparatus and storage medium and electronic equipment of processing business request |
-
2019
- 2019-07-10 CN CN201910623707.0A patent/CN112214699B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130139043A1 (en) * | 2011-11-29 | 2013-05-30 | OneScreen Inc. | System, apparatus and method for updating links |
| CN105162591A (en) * | 2015-07-07 | 2015-12-16 | 腾讯科技（深圳）有限公司 | Equipment registration method and device |
| CN105141605A (en) * | 2015-08-19 | 2015-12-09 | 金蝶软件（中国）有限公司 | Session method, web server and browser |
| CN107743134A (en) * | 2017-11-28 | 2018-02-27 | 湖北三新文化传媒有限公司 | Log-on message processing method, client, server and storage medium |
| CN108769041A (en) * | 2018-06-06 | 2018-11-06 | 深圳壹账通智能科技有限公司 | Login method, system, computer equipment and storage medium |
| CN109218389A (en) * | 2018-07-05 | 2019-01-15 | 东软集团股份有限公司 | The method, apparatus and storage medium and electronic equipment of processing business request |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113448748A (en) * | 2021-06-03 | 2021-09-28 | 北京致远互联软件股份有限公司 | Refreshing method and refreshing system driven by message |
| CN113448748B (en) * | 2021-06-03 | 2023-09-22 | 北京致远互联软件股份有限公司 | Refreshing method and refreshing system driven by message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112214699B (en) | 2023-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20170316781A1 (en) | Remote electronic service requesting and processing method, server, and terminal | |
| CN104765591A (en) | Method and system for updating software configuration parameter, and terminal server | |
| CN104093123B (en) | The information-pushing method of application program, device and system, mobile terminal | |
| CN108834132B (en) | Data transmission method and equipment and related medium product | |
| CN104598262A (en) | Method and device for updating mobile application | |
| CN110569078A (en) | Method and device for preloading webpage-level program | |
| WO2014194759A1 (en) | A method, apparatus, and system for controlling voice data transmission | |
| CN105530239A (en) | Multimedia data obtaining method and device | |
| CN103177217A (en) | File scan method, file scan system, client-side and server | |
| CN113489630A (en) | Network distribution method, device, storage medium and electronic terminal | |
| CN105227598A (en) | A kind of resource sharing method, device and system stored based on cloud | |
| CN107317828B (en) | File downloading method and device | |
| CN111314900B (en) | Wireless connection method, wireless connection device and mobile terminal | |
| CN106020945B (en) | Shortcut item adding method and device | |
| CN111177612B (en) | Page login authentication method and related device | |
| CN110602766B (en) | Personal hotspot identification method and method for determining association relationship between terminals | |
| CN104702643A (en) | A webpage access method, device and system | |
| CN104918130A (en) | Methods for transmitting and playing multimedia information, devices and system | |
| CN112214699B (en) | Page processing method and related device | |
| CN115794654A (en) | Test case distribution processing method, system, equipment and storage medium | |
| CN109002535B (en) | Data updating method and device | |
| CN106657278B (en) | Data transmission method and device and computer equipment | |
| CN106879046B (en) | Network scanning method and terminal equipment | |
| CN110913022A (en) | Method, device and system for downloading network file of mobile terminal and storage medium | |
| CN106610971A (en) | Identifier determination method and apparatus for ZIP files |
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 |