CN111818179A - User request processing method and device, computing equipment and medium - Google Patents
User request processing method and device, computing equipment and medium Download PDFInfo
- Publication number
- CN111818179A CN111818179A CN202010793110.3A CN202010793110A CN111818179A CN 111818179 A CN111818179 A CN 111818179A CN 202010793110 A CN202010793110 A CN 202010793110A CN 111818179 A CN111818179 A CN 111818179A
- Authority
- CN
- China
- Prior art keywords
- session
- identifier
- request
- record
- version
- 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 9
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000004590 computer program Methods 0.000 claims description 16
- 235000014510 cooky Nutrition 0.000 claims description 15
- 230000008859 change Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 239000000758 substrate Substances 0.000 description 2
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- 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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure provides a user request processing method, which can be applied to the financial field or other fields. The method comprises the following steps: receiving a login request from a terminal device; creating a session and acquiring a session record of the session, wherein the session record comprises a session identifier and a version identifier; and storing the session record to the public storage device, and sending the session identifier and the version identifier to the terminal device. The disclosure also provides a processing device of the user request, a computing device and a computer storage medium.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for processing a user request, a computing device, and a computer storage medium.
Background
Currently, when a user performs a session with a server through a terminal device, a session record generated by the session is usually stored in the server for processing the session. The server may obtain the session information of the user according to the session record, so as to process the request of the user according to the session information, for example, determine whether the operation of the user is legal or not. If the user session fails, the user needs to log in again, and a new session record is created by the server every time the user logs in again.
The existing methods have at least the following disadvantages: due to the unstable network or the down of the server, the user's request is sent to a new server, and the session drift occurs. At this time, because the new server does not store the session record, the user session information cannot be acquired, so that a session failure phenomenon occurs, the user needs to log in again, the user experience is affected, and the risk of repeated operation of the user exists.
Disclosure of Invention
One aspect of the present disclosure provides a method for processing a user request, including: receiving a login request from a terminal device; creating a session and acquiring a session record of the session, wherein the session record comprises a session identifier and a version identifier; and storing the session record to a public storage device, and sending the session identifier and the version identifier to the terminal device.
Optionally, the sending the session identifier and the version identifier to the terminal device includes: generating Session according to the Session record; and storing the Session to a public storage device.
Optionally, the sending the session identifier and the version identifier to the terminal device includes: generating Cookie according to the session identifier and the version identifier; and sending the Cookie to the terminal equipment.
Optionally, the method further comprises: receiving a session request from a terminal device, wherein the session request comprises a session identifier and a version identifier; acquiring a target session record from a public storage device according to the session identifier in the session request; judging whether the version identification in the target session record is matched with the version identification in the session request; if the version identification in the target session record is matched with the version identification in the session request, processing the session request according to the target session record; and if the version identification in the target session record is not matched with the version identification in the session request, indicating the terminal equipment to resend the login request.
Optionally, the method further comprises: and responding to the change of the session record, storing the changed session record into a public storage device, and sending the session identifier and the version identifier in the session record to the terminal device.
Optionally, the method further comprises: setting the storage duration of the session record in the public storage device; and deleting the session record in the public storage device if the storage duration of the session record on the public storage device exceeds the storage duration.
Another aspect of the present disclosure provides a device for processing a user request, including: the first receiving module is used for receiving a login request from the terminal equipment; the system comprises a creating module, a judging module and a judging module, wherein the creating module is used for creating a session and acquiring a session record of the session, and the session record comprises a session identifier and a version identifier; and the sending module is used for storing the session record to a public storage device and sending the session identifier and the version identifier to the terminal device.
Optionally, the apparatus further comprises: a second receiving module, configured to receive a session request from a terminal device, where the session request includes a session identifier and a version identifier; the acquisition module is used for acquiring a target session record from a public storage device according to the session identifier in the session request; the judging module is used for judging whether the version identification in the target session record is matched with the version identification in the session request; the processing module is used for processing the session request according to the target session record under the condition that the version identifier in the target session record is matched with the version identifier in the session request; and an indicating module, configured to indicate the terminal device to resend the login request when the version identifier in the target session record does not match the version identifier in the session request.
Another aspect of the disclosure provides a computing device comprising: one or more processors; storage means for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
According to the embodiment of the disclosure, the session record is stored in the public storage device, and when the service server cannot be accessed due to the network and server states, the session record cannot be lost, so that the session failure phenomenon caused by the network and server states can be avoided, the use experience of a user is improved, and the risk of repeated operation of the user can also be avoided.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
fig. 1 schematically illustrates an application scenario of a user request processing method and a user request processing apparatus according to an embodiment of the present disclosure;
FIG. 2 schematically shows a flow chart of a method of processing a user request according to an embodiment of the present disclosure;
FIG. 3 schematically shows a flow chart of a method of processing a user request according to another embodiment of the present disclosure;
FIG. 4 schematically shows a flow chart of a method of processing a user request according to another embodiment of the present disclosure;
FIG. 5 schematically shows a flow chart of a method of processing a user request according to another embodiment of the present disclosure;
FIG. 6 schematically shows a block diagram of a processing device of a user request according to an embodiment of the present disclosure;
FIG. 7 schematically shows a block diagram of a user request processing device according to another embodiment of the present disclosure; and
FIG. 8 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.
The embodiment of the disclosure provides a user request processing method and a user request processing device capable of applying the method. The method comprises the steps of receiving a login request from terminal equipment; creating a session and acquiring a session record of the session, wherein the session record comprises a session identifier and a version identifier; and storing the session record to a public storage device, and sending the session identifier and the version identifier to the terminal device.
It should be noted that the method and apparatus for processing a user request in the embodiments of the present disclosure may be used in the financial field, and may also be used in any field other than the financial field.
Fig. 1 schematically illustrates an application scenario of a user request processing method and a user request processing apparatus according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a scenario in which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, a system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, a server 105, and a common storage device 106. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server that provides various services, such as a business server that provides support for websites browsed by users using the terminal apparatuses 101, 102, 103. The service server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device. For example, the service server may establish or continue a session with the terminal device upon receiving a user request from the terminal device.
The common storage device 106 may be used for storing session information generated by the service server, and may include, for example, a distributed storage device such as Redis, a database device such as Oracle, or a backup server.
It should be noted that the processing method for the user request provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the processing device for the user request provided by the embodiment of the present disclosure may be generally disposed in the server 105. The processing method for the user request provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the processing device for the user request provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Fig. 2 schematically shows a flow chart of a method of processing a user request according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S210 to S230.
In operation S210, a login request from a terminal device is received.
According to an embodiment of the present disclosure, the login request may be used to request the service server to open a new session for the requestor account.
In operation S220, a session is created, and a session record of the session is acquired.
According to an embodiment of the present disclosure, the session record may be used to record relevant information of the session, and may include, for example, a session identifier and a version identifier. The session identifier may be, for example, a session ID, and the version identifier may be, for example, a version number.
In operation S230, the session record is stored to the public storage device, and the session identifier and the version identifier are transmitted to the terminal device.
According to the embodiment of the disclosure, the Session can be generated according to the Session record, the Session record is stored by using the Session, and the Session is stored to the public storage device.
According to an embodiment of the present disclosure, the common storage device may include, for example, a distributed storage device such as Redis, a database device such as Oracle, or a backup server.
According to the embodiment of the disclosure, the Cookie can be generated according to the session identifier and the version identifier, and the Cookie is sent to the terminal equipment. The Cookie includes, for example, a key value pair carried in the request, and may store information such as a session identifier and a version identifier.
According to the embodiment of the disclosure, the session record is stored in the public storage device, and when the service server cannot be accessed due to the network and server states, the session record cannot be lost, so that the session failure phenomenon caused by the network and server states can be avoided, the use experience of a user is improved, and the risk of repeated operation of the user can also be avoided.
Fig. 3 schematically shows a flow chart of a method of processing a user request according to another embodiment of the present disclosure.
As shown in fig. 3, the method may further include operations S310 to S330 in addition to S210 to S230. Operations S310 to S330 may be performed after operation S230, for example.
In operation S310, a session request from a terminal device is received.
According to the embodiment of the disclosure, the session request may be used to request the service server to continue the session with the terminal device. The session request may include, for example, a session identification and a version identification of the most recent session.
In operation S320, the target session record is obtained from the public storage device according to the session identifier in the session request.
In operation S330, it is determined whether the version identifier in the target session record matches the version identifier in the session request, if the version identifier in the target session record matches the version identifier in the session request, operation S340 is performed, and if the version identifier in the target session record does not match the version identifier in the session request, operation S350 is performed.
According to the embodiment of the present disclosure, if the version identifier in the target session record is consistent with the version identifier in the session request or is newer than the version identifier in the session request, it is determined that the version identifier in the target session record matches the version identifier in the session request. If the version identification in the target session record is older than the version identification in the session request, it is determined that the version identification in the target session record does not match the version identification in the session request.
In operation S340, the session request is processed according to the target session record.
According to an embodiment of the present disclosure, in the case that the version identification in the target session record matches the version identification in the session request, the previous session may be continued according to the target session record.
In operation S350, the terminal device is instructed to retransmit the login request.
According to the embodiment of the disclosure, if the version identifier in the target session record is not matched with the version number in the session request, it indicates that there is a omission in the middle, and in order to avoid that the session information is out of date, the user needs to log in again.
According to another embodiment of the present disclosure, as the session between the terminal device and the service server progresses, the session record is updated accordingly. Therefore, when the session record is changed, the changed session record is stored in the public storage device in response to the change of the session record, and the session identifier and the version identifier in the session record are sent to the terminal device, so as to update the session identifier and the version identifier stored in the terminal device.
According to another embodiment of the present disclosure, in order to improve the storage space utilization of the common storage device, a storage duration may be set for the session records in the common storage device, and in a case that the storage duration of the session records on the common storage device exceeds the storage duration, the session records in the common storage device are deleted to release the storage space. Wherein the storage duration of the session record may be set to be the same as the session timeout time.
The methods shown in fig. 2-3 are further described with reference to fig. 4-5 in conjunction with specific embodiments.
Those skilled in the art will appreciate that the following example embodiments are only for the understanding of the present disclosure, and the present disclosure is not limited thereto.
As shown in fig. 4, in the present embodiment, service servers b1, b2 and b3 are provided for processing user requests. All the service servers are connected to one NOS (Network Operating System) server.
When the user logs in, the user sends a login request to the service server through the terminal equipment. And loading the user request to the b1 server according to the load balancing strategy. b1 server creates new conversation, generates Cookie corresponding to user request, and stores conversation ID and conversation version number in Cookie. After the new session is completed, the b1 server sends the session record such as session ID and session version number to the NOS server, and sets the storage holding time to be the same as the session timeout time. And in addition, sending the Cookie back to the terminal equipment as a response.
And updating the session version number in the Cookie and synchronizing the version number to the public storage when the information in the session is changed at the request of the user.
As shown in fig. 5, when the user initiates the request again within the validity period, the session drifts due to the occurrence of network or original b1 server failure, and the like, and the user request is sent to the b2 server. The b2 server analyzes the Cookie in the user request to obtain the session ID in the Cookie. And acquiring the synchronous Session from the NOS server according to the Session ID in the Cookie, and judging whether the Session version number (Session version) of the acquired Session is matched. If the session version numbers are not matched, the missing in the middle is indicated, and in order to avoid the outdated information, the user needs to log in again.
If the Session version numbers are matched, the Session is continued, the Session is modified according to the Session, the modified Session is sent to the NOS equipment, and the Session version of the corresponding service group is added with 1. A Cookie for updating the session version number is attached to the response.
Fig. 6 schematically shows a block diagram of a user request processing device according to an embodiment of the present disclosure.
As shown in fig. 6, the user request processing apparatus 600 may include a first receiving module 610, a creating module 620, and a transmitting module 630. The processing means 600 of the user request may perform the method described above with reference to fig. 2.
Specifically, the first receiving module 610 may be configured to receive a login request from a terminal device.
The creating module 620 may be configured to create a session and obtain a session record of the session, where the session record includes a session identifier and a version identifier.
The sending module 630 may be configured to store the session record in the public storage device, and send the session identifier and the version identifier to the terminal device.
Fig. 7 schematically shows a block diagram of a user request processing device according to another embodiment of the present disclosure.
As shown in fig. 7, the processing apparatus 700 for a user request may further include a second receiving module 710, an obtaining module 720, a judging module 730, a processing module 740, and an indicating module 750, in addition to the first receiving module 610, the creating module 620, and the transmitting module 630. The user requested processing means 700 may perform the method described above with reference to fig. 3.
Specifically, the second receiving module 710 may be configured to receive a session request from a terminal device, where the session request includes a session identifier and a version identifier.
The obtaining module 720 may be configured to obtain the target session record from the public storage device according to the session identifier in the session request.
The determining module 730 may be configured to determine whether the version identifier in the target session record matches the version identifier in the session request.
The processing module 740 may be configured to process the session request according to the target session record when the version identifier in the target session record matches the version identifier in the session request.
The instructing module 750 may be configured to instruct the terminal device to resend the login request if the version identifier in the target session record does not match the version identifier in the session request.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any plurality of the first receiving module 610, the creating module 620, the sending module 630, the second receiving module 710, the obtaining module 720, the determining module 730, the processing module 740, and the indicating module 750 may be combined into one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to the embodiment of the present disclosure, at least one of the first receiving module 610, the creating module 620, the sending module 630, the second receiving module 710, the obtaining module 720, the determining module 730, the processing module 740, and the indicating module 750 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or by a suitable combination of any of them. Alternatively, at least one of the first receiving module 610, the creating module 620, the sending module 630, the second receiving module 710, the obtaining module 720, the determining module 730, the processing module 740, and the indicating module 750 may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.
FIG. 8 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method according to an embodiment of the present disclosure. The computer system illustrated in FIG. 8 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.
As shown in fig. 8, computer system 800 includes a processor 810 and a computer-readable storage medium 820. The computer system 800 may perform a method according to an embodiment of the disclosure.
In particular, processor 810 may include, for example, a general purpose microprocessor, an instruction set processor and/or related chip set and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), and/or the like. The processor 810 may also include on-board memory for caching purposes. Processor 810 may be a single processing unit or a plurality of processing units for performing different actions of a method flow according to embodiments of the disclosure.
Computer-readable storage medium 820, for example, may be a non-volatile computer-readable storage medium, specific examples including, but not limited to: magnetic storage devices, such as magnetic tape or Hard Disk Drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and so on.
The computer-readable storage medium 820 may include a computer program 821, which computer program 821 may include code/computer-executable instructions that, when executed by the processor 810, cause the processor 810 to perform a method according to an embodiment of the present disclosure, or any variation thereof.
The computer program 821 may be configured with, for example, computer program code comprising computer program modules. For example, in an example embodiment, code in computer program 821 may include one or more program modules, including for example 821A, modules 821B, … …. It should be noted that the division and number of modules are not fixed, and those skilled in the art may use suitable program modules or program module combinations according to actual situations, and when the program modules are executed by the processor 810, the processor 810 may execute the method according to the embodiment of the present disclosure or any variation thereof.
According to an embodiment of the present invention, at least one of the first receiving module 610, the creating module 620, the sending module 630, the second receiving module 710, the obtaining module 720, the judging module 730, the processing module 740, and the indicating module 750 may be implemented as a computer program module described with reference to fig. 8, which, when executed by the processor 810, may implement the corresponding operations described above.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
While the disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.
Claims (10)
1. A processing method for user requests comprises the following steps:
receiving a login request from a terminal device;
creating a session and acquiring a session record of the session, wherein the session record comprises a session identifier and a version identifier; and
and storing the session record to a public storage device, and sending the session identifier and the version identifier to the terminal device.
2. The method of claim 1, wherein the sending the session identifier and the version identifier to the terminal device comprises:
generating Session according to the Session record; and
and storing the Session to a public storage device.
3. The method of claim 1, wherein the sending the session identifier and the version identifier to the terminal device comprises:
generating Cookie according to the session identifier and the version identifier; and
and sending the Cookie to the terminal equipment.
4. The method of claim 1, further comprising:
receiving a session request from a terminal device, wherein the session request comprises a session identifier and a version identifier;
acquiring a target session record from a public storage device according to the session identifier in the session request;
judging whether the version identification in the target session record is matched with the version identification in the session request;
if the version identification in the target session record is matched with the version identification in the session request, processing the session request according to the target session record; and
and if the version identification in the target session record is not matched with the version identification in the session request, indicating the terminal equipment to resend the login request.
5. The method of claim 1, further comprising:
and responding to the change of the session record, storing the changed session record into a public storage device, and sending the session identifier and the version identifier in the session record to the terminal device.
6. The method of claim 1, further comprising:
setting a storage duration of a session record in the common storage device; and
deleting the session record in the common storage device if the storage duration of the session record on the common storage device exceeds the storage duration.
7. A device for processing a user request, comprising:
the first receiving module is used for receiving a login request from the terminal equipment;
the system comprises a creating module, a judging module and a judging module, wherein the creating module is used for creating a session and acquiring a session record of the session, and the session record comprises a session identifier and a version identifier; and
and the sending module is used for storing the session record to a public storage device and sending the session identifier and the version identifier to the terminal device.
8. The apparatus of claim 1, further comprising:
a second receiving module, configured to receive a session request from a terminal device, where the session request includes a session identifier and a version identifier;
the acquisition module is used for acquiring a target session record from a public storage device according to the session identifier in the session request;
the judging module is used for judging whether the version identification in the target session record is matched with the version identification in the session request;
the processing module is used for processing the session request according to the target session record under the condition that the version identifier in the target session record is matched with the version identifier in the session request; and
and the indicating module is used for indicating the terminal equipment to resend the login request under the condition that the version identification in the target session record is not matched with the version identification in the session request.
9. A computing device, comprising:
one or more processors;
a memory for storing one or more computer programs,
wherein the one or more computer programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1 to 6.
10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010793110.3A CN111818179A (en) | 2020-08-07 | 2020-08-07 | User request processing method and device, computing equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010793110.3A CN111818179A (en) | 2020-08-07 | 2020-08-07 | User request processing method and device, computing equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111818179A true CN111818179A (en) | 2020-10-23 |
Family
ID=72863732
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010793110.3A Pending CN111818179A (en) | 2020-08-07 | 2020-08-07 | User request processing method and device, computing equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111818179A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112488762A (en) * | 2020-11-30 | 2021-03-12 | 维沃移动通信有限公司 | Advertisement resource processing method, device, equipment and readable storage medium |
| CN115190159A (en) * | 2022-07-08 | 2022-10-14 | 中国工商银行股份有限公司 | Session control method, device, electronic equipment and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140223525A1 (en) * | 2013-02-05 | 2014-08-07 | Ca, Inc. | Access to Vaulted Credentials Using Login Computer and Mobile Computing Device |
| CN106973062A (en) * | 2017-04-27 | 2017-07-21 | 努比亚技术有限公司 | A kind of conversation managing method and server |
| CN107483418A (en) * | 2017-07-27 | 2017-12-15 | 阿里巴巴集团控股有限公司 | Login processing method, service processing method, device and server |
| CN110213356A (en) * | 2019-05-21 | 2019-09-06 | 深圳壹账通智能科技有限公司 | A kind of login process method and relevant device based on data processing |
-
2020
- 2020-08-07 CN CN202010793110.3A patent/CN111818179A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140223525A1 (en) * | 2013-02-05 | 2014-08-07 | Ca, Inc. | Access to Vaulted Credentials Using Login Computer and Mobile Computing Device |
| CN106973062A (en) * | 2017-04-27 | 2017-07-21 | 努比亚技术有限公司 | A kind of conversation managing method and server |
| CN107483418A (en) * | 2017-07-27 | 2017-12-15 | 阿里巴巴集团控股有限公司 | Login processing method, service processing method, device and server |
| CN110213356A (en) * | 2019-05-21 | 2019-09-06 | 深圳壹账通智能科技有限公司 | A kind of login process method and relevant device based on data processing |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112488762A (en) * | 2020-11-30 | 2021-03-12 | 维沃移动通信有限公司 | Advertisement resource processing method, device, equipment and readable storage medium |
| CN115190159A (en) * | 2022-07-08 | 2022-10-14 | 中国工商银行股份有限公司 | Session control method, device, electronic equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7678065B2 (en) | Implementing compliance settings on mobile devices to adhere to configuration scenarios | |
| US11170065B2 (en) | Technology agnostic UI microservices | |
| CN110825479A (en) | Page processing method and device, terminal equipment, server and storage medium | |
| CN111913738A (en) | Access request processing method, device, computing equipment and medium | |
| US11722481B2 (en) | Multiple identity provider authentication system | |
| US9350735B1 (en) | Context-based dynamic information rights management | |
| US20110238924A1 (en) | Webpage request handling | |
| CN110377440B (en) | Information processing method and device | |
| CN111309747A (en) | Data synchronization method, system and device | |
| CN113094211B (en) | Backup data processing method and device | |
| US20200153889A1 (en) | Method for uploading and downloading file, and server for executing the same | |
| CN111338834A (en) | Data storage method and device | |
| Kemp et al. | Professional Heroku Programming | |
| CN111818179A (en) | User request processing method and device, computing equipment and medium | |
| CN112468511A (en) | File transmission method and device | |
| CN113132400B (en) | Business processing method, device, computer system and storage medium | |
| CN113190812A (en) | Login method, system, electronic equipment and storage medium | |
| CN112084114B (en) | Method and apparatus for testing interfaces | |
| CN118449989B (en) | Methods, apparatus, devices, and computer-readable media for invoking business services | |
| US11381665B2 (en) | Tracking client sessions in publish and subscribe systems using a shared repository | |
| US10146885B1 (en) | Method and system for deciding on ordering of scripting language source code for dependency resolution | |
| CN117149248A (en) | Micro front-end construction method, device, equipment and storage medium | |
| CN112783665B (en) | Interface compensation method and device | |
| US20230012904A1 (en) | History preview and shortcut to restore a work scene for a remote app | |
| CN117131295B (en) | Resource management method, system, 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201023 |