CN102082800A - User request processing method and server - Google Patents
User request processing method and server Download PDFInfo
- Publication number
- CN102082800A CN102082800A CN2011100309628A CN201110030962A CN102082800A CN 102082800 A CN102082800 A CN 102082800A CN 2011100309628 A CN2011100309628 A CN 2011100309628A CN 201110030962 A CN201110030962 A CN 201110030962A CN 102082800 A CN102082800 A CN 102082800A
- Authority
- CN
- China
- Prior art keywords
- user
- login
- login record
- request
- record
- 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 abstract 2
- 238000000034 method Methods 0.000 claims abstract description 20
- 238000012217 deletion Methods 0.000 claims description 12
- 230000037430 deletion Effects 0.000 claims description 12
- 238000004321 preservation Methods 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000012467 final product Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
Abstract
The invention discloses a user request processing method and a server, and the method is used for a server side and comprises the following steps: receiving a login request of a user; looking up a login record containing a user identifier carried in the login request; deleting the login record which is looked up when the login record is looked up, generating the login record according to the login request and saving; and generating the login record according to the login request and saving when the login record can not be looked up, wherein the login record contains the user identifier in the login request and a session identifier generated for the login request. By adopting the method and the server, repeated login of the same user can be avoided in a network system, thereby eliminating the risk of operation conflict of system resources.
Description
Technical field
The present invention relates to network field, relate in particular to a kind of user and ask method and the server handled.
Background technology
Be accompanied by popularizing of Internet, B/S (Browser/Server) structure occurred, i.e. browser and server architecture.Under this structure, the user job interface is to realize by Web browser, and few part affairs logic realizes at front end (Browser), but main affairs logic forms so-called three layers of 3-tier structure in server end (Server) realization.In the B/S structure, most of or main service logic all exists and server end, therefore, the system of B/S structure does not need to install client software, it operates on the browser of client, and system upgrade or only need update service device end software to get final product when safeguarding has so just been simplified client computer load greatly, alleviate the cost and the workload of system maintenance and upgrading, reduced user's overall cost.The system that is produced as of B/S structural system provides possibility in the face of unlimited unknown subscriber.
Now a lot of websites need the user to login by browser, just can operate accordingly then; In implementing process of the present invention, may there be following problems in the inventor when finding to adopt the browser login:
Because the sharing of Internet resources has the problem of same user by different viewing page repeat logon usually in web-based system, can bring the risk of system resource operating collision.
Summary of the invention
The technical problem to be solved in the present invention is how to avoid same user's repeat logon in the network system, eliminates the risk of system resource operating collision.
In order to address the above problem, the invention provides a kind of user and ask the method handled, be used for server side, comprising:
Receive login request of users;
Search the login record that comprises the entrained user ID of described logging request;
The login record that deletion is found when finding generates login record and preservation according to described logging request; When searching not then, generate login record and preservation according to described logging request; Described login record comprises the user ID in the described logging request and is the session identification that described logging request generates.
Further, described method also comprises:
Receive user's operation requests;
Search the login record that comprises the entrained user ID of described operation requests;
When the session identification of session identification in the login record that finds and described operation requests is inconsistent, nullify the session identification of this operation requests.
Further, described login record is kept in the user login information tabulation.
Further, described method also comprises:
Monitor each session;
When session failed, deletion comprises the login record of this session identification.
Further, described method also comprises:
Receive user's the request of withdrawing from;
Deletion comprises the described login record that withdraws from the entrained user ID of request.
The present invention also provides a kind of server, comprising: memory module;
Receiver module is used to receive login request of users;
Search module, be used for searching the login record that comprises the entrained user ID of described logging request in described memory module;
Processing module is used for when finding the login record that deletion is found, and generates login record and is kept in the described memory module according to described logging request; When searching not then, generate login record and be kept in the described memory module according to described logging request; Described login record comprises the user ID in the described logging request and is the session identification that described logging request generates.
Further, described receiver module also is used to receive user's operation requests;
The described module of searching also is used to search the login record that comprises the entrained user ID of described operation requests;
Described processing module also is used for nullifying the session identification of this operation requests when the session identification of the session identification of the login record that finds and described operation requests is inconsistent.
Further, described processing module is kept at described login record in the user login information tabulation in the described memory module.
Further, described server also comprises:
Monitor module, be used to monitor each session;
Described processing module also is used for deleting the login record that comprises this session identification in the described memory module when session failed.
Further, described receiver module also is used to receive user's the request of withdrawing from;
Described processing module also is used for deleting described memory module and comprises the described login record that withdraws from the entrained user ID of request.
Technical scheme of the present invention is once logined before making and is withdrawed from automatically when user's repeat logon takes place, and guarantees that there is unique login example in same user in system, thereby can avoid the situation of system resource operating collision to take place.
Description of drawings
Fig. 1 is the schematic block diagram of the server among the embodiment two.
Embodiment
Below in conjunction with drawings and Examples technical scheme of the present invention is described in detail.
Need to prove that if do not conflict, each feature among the embodiment of the invention and the embodiment can mutually combine, all within protection scope of the present invention.In addition, can in computer system, carry out in the step shown in the flow chart of accompanying drawing such as a set of computer-executable instructions, and, though there is shown logical order in flow process, but in some cases, can carry out step shown or that describe with the order that is different from herein.
Embodiment one, and a kind of user asks the method handled, can be used for server side, comprising:
Receive login request of users;
Search the login record that comprises the entrained user ID of described logging request;
The login record that deletion is found when finding generates login record and preservation according to described logging request; When searching not then, generate login record and preservation according to described logging request; Described login record comprises the user ID in the described logging request and is the session identification that described logging request generates.
Described session identification can but to be not limited to be that the WEB server program is the identification strings that each session automatically generates.
In the present embodiment, described user ID can but be not limited to user name, user account etc.; Can but be not limited to described login record is kept in the user login information tabulation.
Present embodiment guarantees that by preservation and inspection to logging request only there is unique login example in same user in system, guarantees that promptly it is effective that the same user of synchronization has only a logging request; And can learn the relevant information of current all login users.
In the present embodiment, described method can also comprise:
Receive user's operation requests;
Search the login record that comprises the entrained user ID of described operation requests;
When the session identification of session identification in the login record that finds and described operation requests is inconsistent, nullify the session identification of this operation requests.
Usually, the browser of nullifying the back client will jump to login interface, so just can realize that back one login offsets the last effect of landing.
The session identification of operation requests is the same with the session identification of logging request, in typical browser is realized, once typical session life cycle is: the user uses browser to ask the user to close browser for the first time to the server transmission, session identification can not change during this period, unless session failed (such as session timeout or cancellation).
After the operation requests that receives the user, if the login record that comprises the entrained user ID of operation requests that can find, and the session identification in this login record is consistent with the session identification of described operation requests, then can carry out follow-up processing according to user's operation requests.
In the present embodiment, described method can also comprise:
Monitor each session;
When session failed, deletion comprises the login record of this session identification.
So just can from the user login information tabulation, delete the user profile record that lost efficacy in time, the consistency of tabulation of maintenance customer's log-on message and actual log state.
In the present embodiment, described method can also comprise:
Receive user's the request of withdrawing from;
Deletion comprises the described login record that withdraws from the entrained user ID of request.
After receiving user's operation requests, if search less than the login record that comprises the entrained user ID of operation requests, illustrate that this session had been lost efficacy or the user withdraws from.
In the present embodiment, described user can but be not limited to send described logging request and operation requests by browser.
Embodiment two, and a kind of server as shown in Figure 1, comprising: memory module;
Receiver module is used to receive login request of users;
Search module, be used for searching the login record that comprises the entrained user ID of described logging request in described memory module;
Processing module is used for when finding the login record that deletion is found, and generates login record and is kept in the described memory module according to described logging request; When searching not then, generate login record and be kept in the described memory module according to described logging request; Described login record comprises the user ID in the described logging request and is the session identification that described logging request generates.
In the present embodiment, described user ID can but be not limited to user name, user account etc.; Described processing module can but be not limited to described login record is kept in the user login information tabulation in the described memory module.
In the present embodiment, described receiver module can also be used to receive user's operation requests;
The described module of searching can also be used to search the login record that comprises the entrained user ID of described operation requests;
Described processing module can also be used for nullifying the session identification of this operation requests when the session identification of the session identification of the login record that finds and described operation requests is inconsistent.
In the present embodiment, described device can also comprise:
Monitor module, be used to monitor each session;
Described processing module can also be used for deleting the login record that comprises this session identification in the described memory module when session failed.
In the present embodiment, described receiver module can also be used to receive user's the request of withdrawing from;
Described processing module can also be used for deleting described memory module and comprise the described login record that withdraws from the entrained user ID of request.
In the present embodiment, described user can send described logging request and operation requests by browser.
Other realizes that details can be with embodiment one.
One of ordinary skill in the art will appreciate that all or part of step in the said method can instruct related hardware to finish by program, described program can be stored in the computer-readable recording medium, as read-only memory, disk or CD etc.Alternatively, all or part of step of the foregoing description also can use one or more integrated circuits to realize.Correspondingly, each the module/unit in the foregoing description can adopt the form of hardware to realize, also can adopt the form of software function module to realize.The present invention is not restricted to the combination of the hardware and software of any particular form.
Certainly; the present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art work as can make various corresponding changes and distortion according to the present invention, but these corresponding changes and distortion all should belong to the protection range of claim of the present invention.
Claims (10)
1. a user asks the method handled, is used for server side, comprising:
Receive login request of users;
Search the login record that comprises the entrained user ID of described logging request;
The login record that deletion is found when finding generates login record and preservation according to described logging request; When searching not then, generate login record and preservation according to described logging request; Described login record comprises the user ID in the described logging request and is the session identification that described logging request generates.
2. the method for claim 1 is characterized in that, also comprises:
Receive user's operation requests;
Search the login record that comprises the entrained user ID of described operation requests;
When the session identification of session identification in the login record that finds and described operation requests is inconsistent, nullify the session identification of this operation requests.
3. the method for claim 1 is characterized in that:
Described login record is kept in the user login information tabulation.
4. as each described method in the claim 1 to 3, it is characterized in that, also comprise:
Monitor each session;
When session failed, deletion comprises the login record of this session identification.
5. as each described method in the claim 1 to 3, it is characterized in that, also comprise:
Receive user's the request of withdrawing from;
Deletion comprises the described login record that withdraws from the entrained user ID of request.
6. a server is characterized in that, comprising: memory module;
Receiver module is used to receive login request of users;
Search module, be used for searching the login record that comprises the entrained user ID of described logging request in described memory module;
Processing module is used for when finding the login record that deletion is found, and generates login record and is kept in the described memory module according to described logging request; When searching not then, generate login record and be kept in the described memory module according to described logging request; Described login record comprises the user ID in the described logging request and is the session identification that described logging request generates.
7. server as claimed in claim 6 is characterized in that:
Described receiver module also is used to receive user's operation requests;
The described module of searching also is used to search the login record that comprises the entrained user ID of described operation requests;
Described processing module also is used for nullifying the session identification of this operation requests when the session identification of the session identification of the login record that finds and described operation requests is inconsistent.
8. server as claimed in claim 6 is characterized in that:
Described processing module is kept at described login record in the user login information tabulation in the described memory module.
9. as each described server in the claim 6 to 8, it is characterized in that, also comprise:
Monitor module, be used to monitor each session;
Described processing module also is used for deleting the login record that comprises this session identification in the described memory module when session failed.
10. as each described server in the claim 6 to 8, it is characterized in that:
Described receiver module also is used to receive user's the request of withdrawing from;
Described processing module also is used for deleting described memory module and comprises the described login record that withdraws from the entrained user ID of request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011100309628A CN102082800A (en) | 2011-01-28 | 2011-01-28 | User request processing method and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011100309628A CN102082800A (en) | 2011-01-28 | 2011-01-28 | User request processing method and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102082800A true CN102082800A (en) | 2011-06-01 |
Family
ID=44088552
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011100309628A Pending CN102082800A (en) | 2011-01-28 | 2011-01-28 | User request processing method and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102082800A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103024040A (en) * | 2012-12-13 | 2013-04-03 | 福建星网锐捷网络有限公司 | Method and system for processing repeated log in of webpage authentication user |
| CN103118092A (en) * | 2013-01-24 | 2013-05-22 | 中国联合网络通信集团有限公司 | Method and device for realizing single login |
| CN103491141A (en) * | 2013-09-04 | 2014-01-01 | 用友软件股份有限公司 | Application server and request processing method |
| CN104660560A (en) * | 2013-11-20 | 2015-05-27 | 腾讯科技（北京）有限公司 | Reporting method and device for authorization statistical information |
| CN106209744A (en) * | 2015-05-07 | 2016-12-07 | 阿里巴巴集团控股有限公司 | Subscriber sign-in conversation management-control method, device and server |
| CN106331155A (en) * | 2016-09-26 | 2017-01-11 | 联动优势电子商务有限公司 | Method for preventing repeated login of user and server |
| CN106534158A (en) * | 2016-11-29 | 2017-03-22 | 努比亚技术有限公司 | Account login control device and method |
| CN106846142A (en) * | 2015-12-07 | 2017-06-13 | 腾讯科技（深圳）有限公司 | A kind of information processing method and server |
| CN106973062A (en) * | 2017-04-27 | 2017-07-21 | 努比亚技术有限公司 | A kind of conversation managing method and server |
| CN110475088A (en) * | 2018-05-09 | 2019-11-19 | 视联动力信息技术股份有限公司 | A kind of method and apparatus that user logs in |
| CN110839041A (en) * | 2019-11-22 | 2020-02-25 | 苏州浪潮智能科技有限公司 | Single-user login method, device, equipment and medium supporting multi-node deployment |
| CN111600858A (en) * | 2020-05-06 | 2020-08-28 | 腾讯科技（深圳）有限公司 | Application login method, device and system |
| CN115987495A (en) * | 2022-12-05 | 2023-04-18 | 南凌科技股份有限公司 | Universal MQTT client id conflict detection and protection implementation system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1540544A (en) * | 2003-04-22 | 2004-10-27 | 联想(北京)有限公司 | Method for tracking and controlling users' online states and information |
| CN101534197A (en) * | 2009-03-23 | 2009-09-16 | 深圳市金蝶移动互联技术有限公司 | Method, device and system for treating user relogin in single-point login system |
| CN101707620A (en) * | 2009-11-26 | 2010-05-12 | 迈普通信技术股份有限公司 | Method and system for detecting repeat login of Web authenticated user |
-
2011
- 2011-01-28 CN CN2011100309628A patent/CN102082800A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1540544A (en) * | 2003-04-22 | 2004-10-27 | 联想(北京)有限公司 | Method for tracking and controlling users' online states and information |
| CN101534197A (en) * | 2009-03-23 | 2009-09-16 | 深圳市金蝶移动互联技术有限公司 | Method, device and system for treating user relogin in single-point login system |
| CN101707620A (en) * | 2009-11-26 | 2010-05-12 | 迈普通信技术股份有限公司 | Method and system for detecting repeat login of Web authenticated user |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103024040B (en) * | 2012-12-13 | 2015-11-25 | 福建星网锐捷网络有限公司 | The method and system of process webpage authenticated user repeat logon |
| CN103024040A (en) * | 2012-12-13 | 2013-04-03 | 福建星网锐捷网络有限公司 | Method and system for processing repeated log in of webpage authentication user |
| CN103118092A (en) * | 2013-01-24 | 2013-05-22 | 中国联合网络通信集团有限公司 | Method and device for realizing single login |
| CN103118092B (en) * | 2013-01-24 | 2015-07-15 | 中国联合网络通信集团有限公司 | Method and device for realizing single login |
| CN103491141A (en) * | 2013-09-04 | 2014-01-01 | 用友软件股份有限公司 | Application server and request processing method |
| CN104660560A (en) * | 2013-11-20 | 2015-05-27 | 腾讯科技（北京）有限公司 | Reporting method and device for authorization statistical information |
| CN104660560B (en) * | 2013-11-20 | 2018-09-18 | 腾讯科技（北京）有限公司 | Authorize the report method and device of statistical information |
| CN106209744A (en) * | 2015-05-07 | 2016-12-07 | 阿里巴巴集团控股有限公司 | Subscriber sign-in conversation management-control method, device and server |
| CN106846142A (en) * | 2015-12-07 | 2017-06-13 | 腾讯科技（深圳）有限公司 | A kind of information processing method and server |
| CN106331155B (en) * | 2016-09-26 | 2019-05-07 | 联动优势电子商务有限公司 | A kind of method preventing user's repeat logon and server |
| CN106331155A (en) * | 2016-09-26 | 2017-01-11 | 联动优势电子商务有限公司 | Method for preventing repeated login of user and server |
| CN106534158A (en) * | 2016-11-29 | 2017-03-22 | 努比亚技术有限公司 | Account login control device and method |
| CN106973062A (en) * | 2017-04-27 | 2017-07-21 | 努比亚技术有限公司 | A kind of conversation managing method and server |
| CN110475088A (en) * | 2018-05-09 | 2019-11-19 | 视联动力信息技术股份有限公司 | A kind of method and apparatus that user logs in |
| CN110475088B (en) * | 2018-05-09 | 2021-06-11 | 视联动力信息技术股份有限公司 | User login method and device |
| CN110839041A (en) * | 2019-11-22 | 2020-02-25 | 苏州浪潮智能科技有限公司 | Single-user login method, device, equipment and medium supporting multi-node deployment |
| CN111600858A (en) * | 2020-05-06 | 2020-08-28 | 腾讯科技（深圳）有限公司 | Application login method, device and system |
| CN111600858B (en) * | 2020-05-06 | 2021-12-14 | 腾讯科技（深圳）有限公司 | Application login method, device and system |
| CN115987495A (en) * | 2022-12-05 | 2023-04-18 | 南凌科技股份有限公司 | Universal MQTT client id conflict detection and protection implementation system |
| CN115987495B (en) * | 2022-12-05 | 2023-09-15 | 南凌科技股份有限公司 | Universal MQTT client id conflict detection and protection implementation system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102082800A (en) | User request processing method and server | |
| CN112637346B (en) | Proxy method, proxy device, proxy server and storage medium | |
| US20210250248A1 (en) | Remote emulation of a storage system | |
| US7793140B2 (en) | Method and system for handling failover in a distributed environment that uses session affinity | |
| US10104037B2 (en) | Method and system for network access request control | |
| US9800691B2 (en) | Stream processing using a client-server architecture | |
| US9712622B2 (en) | Techniques to manage state information for a web service | |
| US10193997B2 (en) | Encoded URI references in restful requests to facilitate proxy aggregation | |
| CN107766343B (en) | Data storage method and device and storage server | |
| US9740537B2 (en) | Contention and selection of controlling work coordinator in a distributed computing environment | |
| JP2014516182A (en) | Cloud service reconnection automation | |
| CN107612950A (en) | A kind of method, apparatus, system, electronic equipment that service is provided | |
| CN105610917B (en) | Method and system for realizing synchronous data repair in system | |
| US8903871B2 (en) | Dynamic management of log persistence | |
| US9621632B2 (en) | Scaling of stateful enterprise services | |
| CN106302667A (en) | Code management system and method | |
| US11381665B2 (en) | Tracking client sessions in publish and subscribe systems using a shared repository | |
| JP2007249295A (en) | Session management program, session management method, and session management apparatus | |
| CN112069137A (en) | Method and device for generating information, electronic equipment and computer readable storage medium | |
| CN111800511A (en) | Processing method, system, equipment and readable storage medium for synchronous login state | |
| US11847161B2 (en) | Data processing method and apparatus, device, and storage medium | |
| US9633120B2 (en) | Continuously blocking query result data for a remote query | |
| CN109302446B (en) | Cross-platform access method and device, electronic equipment and storage medium | |
| US10693826B2 (en) | Message Service | |
| CN111078736A (en) | Data aggregation processing method and device, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110601 |